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

Deal internally with OpenAPI 3 instead of Swagger 2.0 #5

Open
u8sand opened this issue Oct 24, 2018 · 0 comments
Open

Deal internally with OpenAPI 3 instead of Swagger 2.0 #5

u8sand opened this issue Oct 24, 2018 · 0 comments

Comments

@u8sand
Copy link
Owner

u8sand commented Oct 24, 2018

Given that OpenAPI 3 has more features than swagger 2.0, any given swagger 2.0 file can be represented in OpenAPI 3 but not the other way around. In order to ensure feature completeness, it is therefore necessary to utilize OpenAPI 3 instead of Swagger 2.0 internally.

This may ultimately result in throwing away the pyswagger dependency which only works currently with Swagger 2.0

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

1 participant