Repository navigation
Add xpath to validation error details - #168
Merged
Merged
Conversation
|
Coverage after merging add-xpath-to-error into master will be
Coverage Report
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contributor
Author
|
@jameslan let me know if I can do anything to help this along -- thanks |
jameslan
approved these changes
Aug 20, 2026
github-actions Bot
pushed a commit
that referenced
this pull request
Aug 20, 2026
…ror details (#168)"
Owner
|
@msrose Thanks you for your contribution! |
jameslan
pushed a commit
that referenced
this pull request
Sep 5, 2026
* Add xpath to validation error details * Coverage
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
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.
Description
Adds xpath of the error node to the error details.
I have a use case with very large & interconnected XSDs from a third-party -- this library is working great, but it's often tricky to figure out exactly where errors are coming from since I don't control the schemas and (as far as I can tell) there's no way to get the xpath of the error node using existing APIs.
I'm not very familiar with wasm & libxml so please let me know of anything that can be improved here -- the changes make sense to me based on the existing patterns in the codebase, but there are a few tweaks to details that could make sense:
Testing