Open nan01ab opened 2 weeks ago
we use UTF8Strict. Which is UTF8 noBOM i believe with no fallbacks. This is one reason why.
we use UTF8Strict. Which is UTF8 noBOM i believe with no fallbacks. This is one reason why.
\' just ASCII
I been wanting to use the native json libraries System.Test.Json
, for this reason. However all our classes would need to change, by adding attributes to know which properties to expose. However I think the biggest part is the VM. Seeing how no one wanted the VM changed in the pass. But now we are changing the VM so would be good make this change.
JPathToken
doesn't seem to handle the escape-character/escape sequence.For example,
JPathToken
cannot process$.store.book['o\'clock']
Some basic escape characters may need to be handle here. (https://www.rfc-editor.org/rfc/rfc9535#section-2.3.1.2)
Where in the software does this update applies to?