- changed status to resolved
JSON Path implementation issues
Issue #8
resolved
I'm trying to support at least some part of JSON Path.
An issue is the $. that starts a JSON Path. It seems redundant: A.B.C is the same as $.A.B.C, no. However, I'm thinking of requiring the $., as otherwise the User can't have periods in their item names (i.e, "A.B.C" might be the name of an item, not a path).
Comments (1)
-
reporter - Log in to comment
Implemented. $ now required by all public API methods.