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

allow OpenAPI 3.0 #55

Closed
pvdbosch opened this issue Feb 26, 2020 · 2 comments
Closed

allow OpenAPI 3.0 #55

pvdbosch opened this issue Feb 26, 2020 · 2 comments
Assignees
Milestone

Comments

@pvdbosch
Copy link
Contributor

The claim in the guide that OpenAPI 3.0 isn’t supported yet in most tooling is outdated. The API Gateway product that’s offered on gCloud doesn’t offer full support of OpenAPI 3.0 yet however but it is planned.
I don't think this should hold back those already ready for OpenAPI 3.0 however like FPS Mobility.
Customers of OpenAPI 3.0 could use tools to convert to OpenAPI 2.0.

So I propose to also allow 3.0, but add a warning that the guide isn’t optimized for it yet (#31). Most should still apply however.

@pvdbosch pvdbosch added this to the in progress milestone Feb 26, 2020
@pvdbosch pvdbosch self-assigned this Feb 26, 2020
@pvdbosch
Copy link
Contributor Author

pvdbosch commented Mar 25, 2020

eHealth uses https://www.npmjs.com/package/api-spec-converter to convert from OpenAPI 2.0 to 3.0, because it gives better results with code generation. Some manipulation on its input 2.0 file may be required for it to work correctly.

pvdbosch added a commit that referenced this issue Mar 26, 2020
#34: remove styleguidevalidation-rules
@pvdbosch
Copy link
Contributor Author

updated master to allow OpenAPI 3.0

wsalembi pushed a commit that referenced this issue Jul 23, 2020
#34: remove styleguidevalidation-rules
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant