This repository was archived by the owner on Dec 28, 2025. It is now read-only.
"integer" is not a keyword restriction type #84
Merged
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.
Fixes #81, if there's a desire to "fix" it: Keywords can only be restricted to JSON data model types.
The extension keyword API is not an area where people test for compliance, so I'd be equally happy with documenting that
"integer"as an evaluation restriction is ajschonextension, and could post a PR for that if desired. I would also not be upset if this and #81 are just closed and things are left as-is.