You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
When investigating the reason that a large XML failed the validation, looking at only the NodeName might not be enough since there can be too many elements with the same name, for example address.
At the same time, while the error message contains the actual value, so it could be used to identify where the issue lies, it may not be possible to log since that might contain sensitive data.
For that reason a new field is added in StructError that contains the full path to the node that fails the validation. This is reported in reverse order for easier string concatenation. For example: child1<element1<root
When investigating the reason that a large XML failed the validation,
looking at only the NodeName might not be enough since there can be too
many elements with the same name, for example `address`.
At the same time, while the error message contains the actual value, so
it could be used to identify where the issue lies, it may not be
possible to log since that might contain sensitive data.
For that reason a new field is added in StructError that contains the
full path to the node that fails the validation. This is reported in
reverse order for easier string concatenation. For example:
`child1<element1<root`
Hi, thanks for the contribution. While I understand the need I think that the implementation is not very flexible. My opinion is that it would be better to for example return an array of node names, something that one can use however one sees fit without manipulating a string and probably the possibility for further extending without breaking stuff. I already finished the c part for this, will keep you up do date in regard of my progress.
Hi, I just wanted to check if you have an estimate on when the changes will be ready. Is there anything I can do to help?
Was on vacation for a few days and now quite busy in my day job, stalled further progress on this unfortunately. Will probably still take a few more days before I'll have the time to return to this.
Hello, it's been a while since our last discussion so I thought to check again as I am still waiting for this feature to get merged. Do you think you can find some time?
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.
When investigating the reason that a large XML failed the validation, looking at only the NodeName might not be enough since there can be too many elements with the same name, for example
address.At the same time, while the error message contains the actual value, so it could be used to identify where the issue lies, it may not be possible to log since that might contain sensitive data.
For that reason a new field is added in StructError that contains the full path to the node that fails the validation. This is reported in reverse order for easier string concatenation. For example:
child1<element1<root