redoc
redoc copied to clipboard
Redocly
OpenAPI 3.1 support issues
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/elsekeywords from openapi 3.1 are not supported, https://github.com/Redocly/redoc/pull/1939- https://github.com/Redocly/redoc/issues/1643
$refusing$idsupport$refsiblings missing in schemas https://github.com/Redocly/redoc/issues/1727- #1727
- https://github.com/Redocly/openapi-cli/issues/629
- TBD
https://github.com/Redocly/redoc/issues/1761 https://github.com/Redocly/redoc/issues/1788
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.
It looks like OpenAPI 3.1 added support for scopes in authentication schemes other than oauth (https://github.com/OAI/OpenAPI-Specification/issues/1366)
Using both 0.13.10 as well as the live demo (https://redocly.github.io/redoc/), the rendered HTML file does not seem to include scopes for API Key authentication methods in the list of authentication methods.
Strings included in the individual "route" level security array are rendered in the HTML output.
Support for unevaluatedProperties.
https://github.com/Redocly/redoc/issues/1955
