[simonkundrik]

Quoted names are not looked up as written when they contain a bracket, a semicolon, a caret, an apostrophe inside double quotes, a leading double quote or at sign, or a hash followed by a digit. toPathArray splits the expression at those characters before the name is read:

• $['cd[DataLayer]'] and $[']'] return nothing (Selecting properties containing a square bracket seems to be impossible #225), and so does $..['phoneNumbers [1]'] (Path not found when square Brackets inside of Path String #167)
• $["it's"] and $["'lastName'"] return nothing (Cannot resolve JSONPath has single quote #203). $["a'"] is one of the failing cases in the RFC 9535 compliance suite
• $['x;y'] and $['a^b'] return nothing
• $['@id'] throws at the root (Error thrown when using square brackets to access property at the root of the JSON #258), and $['Name#23'] throws Cannot read properties of undefined (Errors in case of special characters like '#' and undefined output with square brackets while using 'JSONPath' #173)
• the paths JSONPath returns for such properties (resultType: 'path') can't be passed back in, and neither can the array form ['$', 'a[b]']

A single quoted name with one of those characters is now kept intact in toPathArray, with a leading backtick (the existing escape, so it works like $.*and$['*']) and looked up as it is. Names without them take the same route as before, so their toPathArray output doesn't change either, and $['*'] is still a wildcard. A name that already starts with a backtick keeps its escape meaning.

A name that starts with ( is still read as a script (that happens earlier), and unquoted $.Name#23 still fails, so #173 is only partly covered.

I know #259 reworks the path parser and lists these issues. This is a small change to the current tokenizer for the quoted cases so they work in the meantime. It doesn't touch the lines #291 and #292 change, and I ran the suite on all three branches merged together (all passing).

I added one test to test.properties.js that runs 12 names (in both quote styles where possible) through direct, nested, continued and descendant paths, wrap: false, result path round trips and array paths. It fails on main (both VM modes) and passes now. eslint, tsc and the mocha suite pass and coverage of src stays at 100%. The only failures are the 2 cli tests, which can't run bin/jsonpath-cli.js on my Windows machine, same as on main. Across every path string in the test files the only result that changed was the new test's own backtick case, and in the RFC 9535 suite only $["a'"] changed (it passes now).