Support exclusive constraints in schema #11
Merged
Conversation
This file contains 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
This was referenced Jan 6, 2024
|
ACCEPTED by WG (8/9) |
Deploying with
|
| Latest commit: |
9ccd3d2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9cbb57b4.datapackage.pages.dev |
| Branch Preview URL: | https://856-exclusive-constraints.datapackage.pages.dev |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rationale
Although in the linked discussion there are valid arguments for using a
hackinstead of adding new constraints, I think that's just the right thing to do as the range and exclusive range are two standard constraints for numeric types (see JSONSchema - https://json-schema.org/understanding-json-schema/reference/numeric). New constraints are relatively simple to support in implementations