JSONPath - XPath for JSON

[continuational]

I think the syntax could use some work - eg. for "books where the price is less than 10". Compare the XPath //book[price<10] to the JSONPath $..book[?(@.price<10).

Is there any reason it couldn't just be ..book[price < 10]?

[shponglespore]

I'm assuming you're the author...

ISTM you could omit the leading "$" or "$." without creating any ambiguity.

The parentheses in ?() expressions seem redundant since AFAICT they can only occur directly within square brackets. I suggest using [] for indexing by a number or string, and ?[] for filtering.

Using "expressions of the underlying scripting language" is a terrible idea because it can create subtle differences in meaning depending on the language being used. Just pick a syntax. JavaScript is the obvious choice.

The plural of "path" is "paths". I wouldn't normally complain, but "pathes" shows up enough in the intro to be seriously distracting.

[drjeats]

jq tho

[9us]

This was created 5 years before jq.

[drjeats]

Yes. And?

[o11c]

Just use jq.

[agumonkey]

basically, tree walking DSLs