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
>constptr=require('json-ptr')undefined>badPointer=newJsonPointer("/I'm/bad")JsonPointer{path: ['I\'m','bad']}>badPointer.get({})// expecting this to return undefined
Thrown:
SyntaxError: Unexpectedidentifier>badPointer=newJsonPointer(["I'm","also","bad"])JsonPointer{path: ['I\'m','also','bad']}>badPointer.get({})// expecting this to return undefined
Thrown:
SyntaxError: Unexpectedidentifier
Looks like RFC 6901 mentions that quotes must be escaped in paths, but I couldn't find anything in the json-ptr docs that mentioned what is or isn't escaped by the library. Worth mentioning that it seems to work with other tricky inputs - for example, forward slashes in paths seem to be handled correctly.
The text was updated successfully, but these errors were encountered:
Short repro via REPL using json-ptr 2.0.0:
Looks like RFC 6901 mentions that quotes must be escaped in paths, but I couldn't find anything in the
json-ptr
docs that mentioned what is or isn't escaped by the library. Worth mentioning that it seems to work with other tricky inputs - for example, forward slashes in paths seem to be handled correctly.The text was updated successfully, but these errors were encountered: