-
Notifications
You must be signed in to change notification settings - Fork 9k
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 #5891
Comments
This appears to be the list of what will be in 3.1.0: OAI/OpenAPI-Specification#2025 |
3.1 RC has been released. It would be nice if Swagger UI could support it when the final version is out. |
Is this being worked on actively? If so, is there an estimated release date? |
Any update? |
Just encountered a blocker with this trying to add request bodies to an HTTP DELETE method while upgrading docs. I had thought this was supported but didn't realize there is a sort of mismatch between OpenAPI versions and what SwaggerUI actually supports! |
Does this depend on adding 3.1 support to Swagger Parser? swagger-api/swagger-parser#1535 It looks like a lot of downstream projects are depending on 3.1 support from one or both of Swagger Parser and Swagger UI. Maybe it'd be a good idea to engage with some of them? |
I'm willing to put in some effort over the next several weeks to help get the Swagger UI working with 3.1, but I'm not sure how to assist with that. I don't see any other open issues or pull requests about 3.1, and it looks like there's a major effort with the 4.x release so maybe that work needs to settle first? |
Hi guys, As mentioned in https://swagger.io/blog/api-design/what%E2%80%99s-ahead-for-swaggerui-v4-and-swaggereditor-v4/, 4.x release is the first step of OAS 3.1 adoption. |
Now that v4 has been released, is there any other tracking issue or any support needed? |
eagerly waiting! |
Topic update: Released a blog post with information and updates regarding our work towards OpenAPI 3.1 across various Swagger projects. https://swagger.io/blog/swagger-support-for-openapi-3-0-and-openapi-3-1/ |
@frankkilcommins could you let us know when there's a branch that's started / has some progress on it so that the community can start throwing our 3.1 specs at it to provide as much testing as possible? |
relates |
Hey, thanks for the work so far. Missing feature: Right now the object description renderer cannot handle |
Looks like the support won't be out until version 5. I just tried v5.0.0-alpha.0 and it worked with OpenAPI 3.1.0! |
|
@Ongy |
Thanks for the excellent work on implementing Open Api 3.1 support. |
@PatchRanger thanks for the report. I've created #8525 to track it, let's discuss it futher there. |
[email protected] has just been released! |
While the spec is not final yet, i'd be nice to have some support eventually. It eliminates some inconsistencies between OpenAPI and JSON Schema.
https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md
https://apisyouwonthate.com/blog/openapi-v3-1-and-json-schema
The text was updated successfully, but these errors were encountered: