reject unterminated key predicates in extractKV - #1095
Open
nabhan06 wants to merge 1 commit into
Open
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
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.
extractKV doesn't check whether it is still inside a [key=value] predicate when the input runs out, so an element with a dangling predicate is silently mis-parsed rather than rejected: the element name is discarded and the trailing key value takes its place. StringToStructuredPath(
/a/b[k=c) returns /a/c with no error, and PathToSchemaPath on a deprecated Element ofa[b=creturns /c, so code that string-checks a path before converting it can end up resolving a different node than the one it inspected. Same story for a trailing escape character, where the backslash is just dropped.This errors on both cases at the end of extractKV, with test cases covering the string and Element forms.