For some unknown reasons, the {%x7B opening brace character seems to be omitted from the list of valid characters.
I believe this is an error and cannot find any justification.
The JSON grammar specifies that all characters in the range %x20-10FFFF are valid. (except \%x5C escape character).
The only exception for JMESPath is the need to escape the `%x60 (backtick) character.
This PR re-introduces the { as a valid character.
This PR also fixes a mistake while specifying the json-quoted-string which does not currently support empty strings.
The
unescaped_literal
grammar rule supports JSON strings when embedded in JMESPath expressions. It current definition is:For some unknown reasons, the
{
%x7B
opening brace character seems to be omitted from the list of valid characters. I believe this is an error and cannot find any justification.The JSON grammar specifies that all characters in the range
%x20-10FFFF
are valid. (except\
%x5C
escape character). The only exception for JMESPath is the need to escape the`
%x60
(backtick) character.This PR re-introduces the
{
as a valid character. This PR also fixes a mistake while specifying thejson-quoted-string
which does not currently support empty strings.