The system consider path as valid if the closed apostrophe is missing

[Swyatoslaw]

Javascript JMESPath library can allow write filter expression without closed apostrophe sign.

For example, in expression
a == 'foo d
for json object
{"a": "foo d", "b": "bar"}
the result will be true and expression can valid.

But, if we try apply it expression in Java JMESPath library, it will be thrown exception:
io.burt.jmespath.parser.ParseException: Unable to compile expression "a == 'foo d": syntax error token recognition error at: ''foo d' at position 5, syntax error mismatched input '<EOF>' expecting {'!', '(', '*', '[', '{', '[?', '@', '', RAW_STRING, JSON_CONSTANT, NAME, STRING} at position 11`
In my opinion, it is bug of Javascript JMESPath library parser, because in JMESPath documentation nowhere write about user can missed closed apostrophe sign.

Using versions:
Javascript JMESPath library: 0.15.0
Java JMESPath library: 0.5.0