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

add tests to ensure that API specs are OpenAPI 3.0 compliant #1085

Open
bhearsum opened this issue Dec 20, 2019 · 0 comments
Open

add tests to ensure that API specs are OpenAPI 3.0 compliant #1085

bhearsum opened this issue Dec 20, 2019 · 0 comments

Comments

@bhearsum
Copy link
Contributor

We've recently started using OpenAPI-style specs to define both our admin and public APIs. We use Connexion to load and create routes for them in Flask. It turns out that Connexion has some extensions that make it possible for us to have Connexion-compatible specs that aren't OpenAPI 2.0 compliant. The consequence of this is that we cannot make use of other OpenAPI 2.0 tools, such as https://github.com/swagger-api/swagger-codegen.

We're still working on becoming OpenAPI 2.0 compliant, but we should add tests to make sure it doesn't regress once we get there.

(Imported from https://bugzilla.mozilla.org/show_bug.cgi?id=1387063)

Need to wait for #1084 first.

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