Hey I noticed when trying to match a JMESPath expression that uses raw string literals with more than one escaped single quote, the matching fails. According to the proposal: https://jmespath.org/proposals/raw-string-literals.html :
"This proposal states that single quotes in a raw string literal must be escaped with a backslash."
And in the spec:
raw-string-escape = escape ("'" / escape)
When trying to match an expression with only one escaped single quote, it succeeds. If I add more than one, it fails to match but still compiles.
Example: JMESPath Expression: contains(['something\\''],a)
This returns true if a equals something'.
If I add an additional escaped single quote, matching fails.
Example: JMESPath Expression: contains(['some\\'thing\\''],a)
This should match if a equals some'thing' but does not.
Hey I noticed when trying to match a JMESPath expression that uses raw string literals with more than one escaped single quote, the matching fails. According to the proposal: https://jmespath.org/proposals/raw-string-literals.html :
"This proposal states that single quotes in a raw string literal must be escaped with a backslash."
And in the spec:
raw-string-escape = escape ("'" / escape)When trying to match an expression with only one escaped single quote, it succeeds. If I add more than one, it fails to match but still compiles.
Example: JMESPath Expression:
contains(['something\\''],a)This returns true if
aequalssomething'.If I add an additional escaped single quote, matching fails.
Example: JMESPath Expression:
contains(['some\\'thing\\''],a)This should match if
aequalssome'thing'but does not.