-
Notifications
You must be signed in to change notification settings - Fork 9.1k
JSON Schema for Responses object is incorrect in light of extensions #2833
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
related: #2799 |
@karenetheridge how did you address this in #2799? It seems like extension properties would satisfy your |
karenetheridge
added a commit
to karenetheridge/OpenAPI-Specification
that referenced
this issue
Dec 11, 2022
karenetheridge
added a commit
to karenetheridge/OpenAPI-Specification
that referenced
this issue
Dec 11, 2022
karenetheridge
added a commit
to karenetheridge/OpenAPI-Specification
that referenced
this issue
Dec 11, 2022
karenetheridge
added a commit
to karenetheridge/OpenAPI-Specification
that referenced
this issue
Dec 11, 2022
Yes, there is no Actually, I thought of a way... I have submitted it as #3093. \o/ |
karenetheridge
added a commit
to karenetheridge/OpenAPI-Specification
that referenced
this issue
Dec 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The 3.0.3 spec says this about the Responses object:
3.1.0 says something similar:
Here's the JSON Schema for 3.0.3:
Note that the
minProperties
attempts to enforce the restriction noted above, but it inadvertently counts extensions. In other words, the following is valid according to the schema, but not according to the spec:Note that 3.1 doesn't appear to try to enforce this in the schema:
The text was updated successfully, but these errors were encountered: