-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 3.1 support issues #1715
Comments
It would be great if the README could elaborate on what "basic" OpenAPI 3.1 support means. What is it lacking in comparison to the premium variant? It would help understand the limitations better. |
@m-mohr the known issues are posted above. Did you find something else? If so, please report the issue and also the link into this tracking issue. Thank you. |
@adamaltman No, I have no specific issues, but the README implies that there are limitations in the Redoc community edition: The "(basic)" implies that there are limitations or so to Redoc CE. I'm wondering what the differences are. If there are no differences, I guess the "(basic)" should be removed? Otherwise, it would be nice to document what is missing so that people can understand what is missing and whether it's worth upgrading/switching/PRing or so. |
Does |
It looks like OpenAPI 3.1 added support for Using both Strings included in the individual "route" level |
Support for |
Add support |
I've just run into the |
can you give an example of your $ref issue? what, exactly, are you referring to? |
We've released support for openapi 3.1 in the RC.54
This is an umbrella issue to track the issues about it.
Known issues
if
/then
/else
keywords from openapi 3.1 are not supported, feat: support conditional operators #1939$ref
using$id
support$ref
siblings missing in schemas OpenAPI 3.1: Missing description when $ref used #1727The text was updated successfully, but these errors were encountered: