We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Vocabulary can be found here: https://json-schema.org/draft/2020-12/json-schema-core#section-10
Keywords such as if, which are not present in the 3.0 vocabulary, are left untouched as arrays.
To support 3.1 these keywords should be turned into Schema objects.
Since OpenAPI 3.0 only supports custom keywords that are prefixed with "x-" I think it should be safe to support these keywords without breaking backwards compatibility.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Vocabulary can be found here: https://json-schema.org/draft/2020-12/json-schema-core#section-10
Keywords such as if, which are not present in the 3.0 vocabulary, are left untouched as arrays.
To support 3.1 these keywords should be turned into Schema objects.
Since OpenAPI 3.0 only supports custom keywords that are prefixed with "x-" I think it should be safe to support these keywords without breaking backwards compatibility.
The text was updated successfully, but these errors were encountered: