-
Notifications
You must be signed in to change notification settings - Fork 9.1k
OAS 2.1 #1477
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
Comments
@heldersepu thanks for the proposal. While it may not be too complicated to publish a 2.1 version, given that 2.0 was published a long time ago, and 3.0.0 was published in the summer, we would rather encourage users and vendors to move to that version rather than issue an intermediate version that will require additional support. We've had a discussion about it in our weekly meeting, and there's general consensus this is not the right path for the project. |
I understand the push to 3.0 but that version is not backward compatible with 2.0. |
But that's a tooling issue, not a spec one. Releasing a 2.1 would require more resources than we have, and it would also require additional resources from tool vendors to support 2.1 as well. This will set back support for OAS3, instead of pushing it forward. |
For what it's worth, I have found the following https://github.com/dutradda/OpenAPI-Specification-2.1/blob/master/README.md |
Any chance we can get an OAS 2.1 ?
Would like to see
example
on the Parameter ObjectJust like we are doing for the OAS 3 Parameter Object
Perhaps we can add a few other optional fields that will not break 2.0 backward compatibility
The text was updated successfully, but these errors were encountered: