-
Notifications
You must be signed in to change notification settings - Fork 422
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 in the model #1147
Comments
Related: swagger-api/swagger-ui#5891 |
So far, I added new fields for 3.1.0 OpenAPI model. |
We have to wait until Swagger supports 3.1 |
Is it a possibility that tapir maintains support for both 3.0.x and 3.1 for some time? I understand Swagger is the immediate blocker, but even after that there might be other tooling that may still be stuck on 3.0.x 🤔 I'm a bit careful with this request though, because it will be a burden for the maintainers of this repository. |
@yoohaemin I think we'll rather switch to 3.1 at some point. Maintaining two branches might be problematic. But not impossible - would be a matter of creating two separate documentation interpreters. |
But please vote on the issue (with 👍 ) so that we can see how popular it is :) |
We've switched from swagger-ui to stoplight elements, as it gives a much nicer view of our API, and stoplight elements supports openapi 3.1 |
This is already done in the model, will be supported once swagger 5.0 is done in #2958 |
https://github.com/OAI/OpenAPI-Specification/releases/tag/3.1.0
The text was updated successfully, but these errors were encountered: