4 ms·
I was wondering how this differs from JSONPath, found some answers on google: > jsonpointer just defines how to access to a single value inside a json document
by nighthawk454 4y ago
I was wondering how this differs from JSONPath, found some answers on google:
> jsonpointer just defines how to access to a single value inside a json document, whereas jsonpath has more powerful features like union (extract multiple values), filters and deep search (recursively match a path).
> But jsonpath is missing a proper specification, so some behaviors are implementation specific with some parts heavily depending on some javascript constructs (mainly filters).
https://github.com/yalp/jsonpath/issues/1#issuecomment-137081081 https://github.com/yalp/jsonpath/issues/1#issuecomment-13708...
- beached_whale 4y agoA simple subset of JSONPath is nice, it looks just like code. e.g foo.bar[5].value and encodes that we expect a member name or a indice into the array or class. It’s common to have numeric string member names in JSON when dealing with associative structures of KV pairs.
- fanf2 4y agoThere is an IETF working group developing a spec for jsonpath https://datatracker.ietf.org/wg/jsonpath/documents/ https://datatracker.ietf.org/wg/jsonpath/documents/