-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
OpenAPI v3.1.0 Support #1302
Comments
Here is the respective release for OpenAPI 3.1: https://github.com/OAI/OpenAPI-Specification/releases/tag/3.1.0-rc0 Using the new JSON schema specification: https://json-schema.org/draft/2019-09/release-notes.html |
OpenAPI v3.1 will be rather tricky for Spectral to implement for a few reasons:
I had a few attempts at various solutions, such as running AJV v6 & v7 simultaneously with npm aliases, but that was a bit of a nightmare and wasn't going to work. I've made a little progress over here: #1399 and we'll keep chipping away at this problem, whilst we help various dependencies upgrade and try to get a finalized meta schema sorted out. We might split the work in two, just get Spectral working as expected for 3.1, then start making new rules for new features later, but I wanted to join up this thread and PR and give some context on what is taking a while. |
Out of curiosity @philsturgeon , you say that the OAS v3.1 meta-schema is based on JSON Schema 2019-09, but the v3.1 spec says that the schema object is a superset of JSON Schema (Draft) 2020-12. What am I missing? |
Yep that’s correct. 2020-12 was just released and nothing supports it yet so aiming for 2019-09 gets us where we need to be. |
Bump: OAS v3.1 was released on 16 February: https://github.com/OAI/OpenAPI-Specification/releases/tag/3.1.0 |
Yes we were involved in the release of OpenAPI v3.1. No need to bump the issue. It’ll be ready when it’s ready. Most tools don’t support it yet: https://OpenAPI.tools |
User story.
As a user, I want to validate against the new version of openapi spec, e.g. while building support for webhooks. The spec isn't official yet though, so it might change and therefore so might the rule!
Is your feature request related to a problem?
I want to add OpenAPI 3.1.0 support to another tool I maintain and to my specs but if I do that, I can't validate them any more with Spectral.
Describe the solution you'd like
Support for new features, such as a draft custom ruleset or branch of spectral I could use (and offer feedback on, obviously)
Additional context
Spectral is great and your community loves you ❤️
The text was updated successfully, but these errors were encountered: