Expose failing JToken in ValidationError #1692
Merged
Conversation
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
Exposing the JToken that failed the error will allow NJsonSchema to better leverage validation errors by accessing the value that failed the schema.
This was referenced Oct 16, 2025
This was referenced Oct 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Hi there. A very small PR that would greatly improve how I can post-process validation errors 🙂
Exposing the JToken that failed the error will allow NJsonSchema users to access various information, including the actual content of the failed token.
For example, when you have a "StringExpected" error, you can quickly access
ValidationError.Tokento see what is the actual value that is not a string. Especially handy for investigating non-nullable field that received a null value.