Custom format validators now have access to the unprocessed properties #301
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
There can be some use cases where a custom format validator requires additional setup values in order to tweak its behaviour. So, now custom format validator have access to the unprocessed properties in the JSON Schema context where the subject is being evaluated.
In order to keep backward compatibility, the new code has been spread among AbstractFormatValidator, FormatValidator and ContextualFormatValidator
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.
There can be some use cases where a custom format validator requires
additional setup values in order to tweak its behaviour. So, now custom
format validator have access to the unprocessed properties in the
JSON Schema context where the subject is being evaluated.
Also, a test has been added to check the new feature