Added custom validator to extend validation exceptions #429
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
saramonzon
approved these changes
Mar 11, 2025
|
I've approved the PR, but could you add a test, so the json is validated even if some integer value is not provided? |
|
Yes, I'll open another issue to add a test |
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.
This update enhances the JSON Schema validation process by allowing the string "Not Provided" as a valid input for numeric fields (integer, number) and date-formatted strings (string, format: date). The new implementation integrates validate_with_exceptions(), which filters out specific type errors while ensuring all other validation rules remain enforced. This approach maintains strict schema validation while introducing flexibility for missing values, improving data handling without modifying the schema structure.
Closes #425