feat: implement numeric exclusive bounds handling for JSON schema draft 07 and above#74
Merged
Merged
Conversation
add adapter for OAS 3.0 to 3.1 comparison
…ccepted values set expanded as `risky` instead of `breaking` in `response` scope maximum, minimum, exclusiveMaximum, exclusiveMinimum (both JSON Schema 04 and above variances)
JayLim2
reviewed
May 12, 2026
JayLim2
approved these changes
May 19, 2026
makeev-pavel
approved these changes
May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat: implement numeric exclusive bounds handling for JSON schema draft 07 and above
feat: classify changes to number validation keywords that result in accepted values set expanded as
riskyinstead ofbreakinginresponsescopemark-maximum-value-as-inclusive-for-number-propertymark-minimum-value-as-inclusive-for-number-propertyincrease-maximum-for-number-propertyremove-maximum-for-number-propertydecrease-minimum-for-number-propertyremove-minimum-for-number-propertyrefactor: add compatibility suite tests for numeric exclusiveMinimum/exclusiveMaximum
change-from-exclusive-maximum-to-inclusive-maximumchange-from-exclusive-minimum-to-inclusive-minimumchange-from-inclusive-maximum-to-exclusive-maximumchange-from-inclusive-minimum-to-exclusive-minimumremove-exclusive-minimumremove-exclusive-maximumincrease-exclusive-maximum-valuedecrease-exclusive-maximum-valueincrease-exclusive-minimum-valuedecrease-exclusive-minimum-valueadd-exclusive-minimumadd-exclusive-maximumreplace-boolean-exclusive-maximum-to-numericreplace-boolean-exclusive-minimum-to-numeric