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
Please consider refactoring the compliance tests to forbid the use of C0 control characters in JMESPath expressions, as it Seems that was never the intended spirit when introduced in JEP-12.
Note: this will break non-conforming implementations.
The text was updated successfully, but these errors were encountered:
Migrated from #14.
The following compliance tests illustrated using control characters, such as line feed in
raw-string
literals.jmespath.test/tests/literal.json
Lines 154 to 161 in aa6fb5f
newline␊
'\n'
"\n"
␊
'\n'
"'" %x0A "'"
'\n'
"newline\n"
However, those expressions are not valid as per the
raw-string-char
grammar rule:Please consider refactoring the compliance tests to forbid the use of C0 control characters in JMESPath expressions, as it Seems that was never the intended spirit when introduced in JEP-12.
Note: this will break non-conforming implementations.
The text was updated successfully, but these errors were encountered: