Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Export as OpenApi 3.0 #1612

Closed
sbeyeler opened this issue Jul 25, 2019 · 5 comments
Closed

[Feature Request] Export as OpenApi 3.0 #1612

sbeyeler opened this issue Jul 25, 2019 · 5 comments
Labels
stale Bot: Stale Issue

Comments

@sbeyeler
Copy link

[Feature Request]
It would be hugely beneficial to be able to export an Insomnia workspace into the OpenApi (open-sourced Swagger) spec. There is currently a pretty big hurdle to taking an Insomnia workspace and putting it on a API documentation website, as most of the bigger ones out there take an OpenApi spec to automatically generate documentation.

Slate can convert from OpenApi
Apiary supports their in-house as well as OpenApi
Azure can import from OpenApi
Apigee can create an api-proxy from OpenApi spec

This would also allow a more interoperable ecosystem, as I could send my insomnia workspaces to other teams who are not using Insomnia, allowing them to use their tool of choice to test our APIs. This is the key sticking point when it comes to getting approval for purchasing the Teams package as a company - as we don't want to promote a tool that will lock us into a specific ecosystem.

@welcome
Copy link

welcome bot commented Jul 25, 2019

👋 Thanks for opening your first issue! If you're reporting a 🐞 bug, please make sure
you include steps to reproduce it. If you're requesting a feature 🎁, please provide real
use cases that would benefit. 👪

To help make this a smooth process, please be sure you have first read the
contributing guidelines.

@stale
Copy link

stale bot commented Sep 23, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Bot: Stale Issue label Sep 23, 2019
@stale stale bot closed this as completed Sep 30, 2019
@misaku
Copy link

misaku commented Oct 9, 2019

i would like see this too, because to be easy make documentation of project

@abitrolly
Copy link

@misaku need to open another issue.

@gschier
Copy link
Contributor

gschier commented Dec 12, 2019

See #1778

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Bot: Stale Issue
Projects
None yet
Development

No branches or pull requests

4 participants