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

Swagger has not existed for four years #872

Closed
philsturgeon opened this issue Feb 22, 2019 · 4 comments
Closed

Swagger has not existed for four years #872

philsturgeon opened this issue Feb 22, 2019 · 4 comments

Comments

@philsturgeon
Copy link

Howdy folks! I know you are still only supporting OpenAPI v2.0 (as read in #815), but I see the word Swagger floating around a lot and I wondered if there was any chance we could catch up on the 2015 renaming to OpenAPI?

Out of interest, is there a roadmap for supporting OpenAPI v3.0? It's quite a big improvement on v2.0, and it would be great to see this modern tool supporting modern API standards.

@achew22
Copy link
Collaborator

achew22 commented Feb 22, 2019

@philipithomas, unfortunately we don't have a roadmap. Maybe this is something you could help out with? For example, I've not yet found something that we can express in the Google http annotations that don't fit nicely into OpenAPI v2. Are there any pieces that you're aware of that don't translate well?

@johanbrandhorst
Copy link
Collaborator

As for the renaming, we could potentially rename the generator and some of the internals to align with the new name but we'd probably still want to make sure we produce a protoc-gen-swagger with every release to avoid confusing users. That sounds like a "good first PR" opportunity to me :).

@klesniewski
Copy link

Seems to be duplicate of #675

@johanbrandhorst
Copy link
Collaborator

Good shout @klesniewski

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

No branches or pull requests

4 participants