-
-
Notifications
You must be signed in to change notification settings - Fork 211
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
Support for OpenAPI 3.1.0 #755
Comments
It seems they have done the work, but have not yet released it as an update: |
OpenAPI 3.1 support is blocked on AJV implementing it, even if this library updates: OAI/OpenAPI-Specification#2689 |
@essential-randomness would it possible to have a version that works without $dynamicAnchor and $recursiveAnchor ? |
Ah, man, I wish. There may be some movement on the AJV issue since yesterday, and if I understand correctly they offered a bounty. As far as my exploration went, I don't think it's possible to do anything about this without the AJV issue being resolved. |
@essential-randomness sorry, I didn't dig into the implication of $dynamicAnchor and $recursiveAnchor. |
@essential-randomness I'm really curious, it seems that fastify-openapi-glue succeed to have the openapi 3.1.0 specification working: To be honest I didn't test it but according to some colleagues, it works well. |
From there:
I have no idea of the implications of this, nor would know what this conversion entails, but this is how they seem to be doing it. |
Still nothing? |
It would be cool to have features like unevaluatedProperties from draft 2019-9. I tried to change the draft, but I may need to spend more time if nothing happens on this issue. @cdimascio Is this update on the roadmap? |
I think this is a duplicate of this issue. |
As I posted about on the above issue, is it possible for this library to take on the preprocess step to resolve $dynamicRef before calling out to AJV? If not, would it be possible to provide a solid reason why it belongs in AJV to respond and continue pushing this forward? |
This is a duplicate of #573 |
Closing this in favor of the duplicate: #573 |
Hi, are there plans to support OpenAPI 3.1.0 with this library?
We're currently running into issues when validating the API spec because Stoplight API exports are using features exclusive to 3.1.0. Mainly trying to avoid workarounds where we manually downgrade the OA version and remove the said block post-export.
The specific feature being a change to the
Schema
definition to containexamples
Thank you!
The text was updated successfully, but these errors were encountered: