3 ms·
Probably. You tell us :=) The incompatibility is apparently due to the fact that jq is happy with a concatenation of JSON objects and q is not. For example {'f
by jeffbee 6y ago
Probably. You tell us :=)
The incompatibility is apparently due to the fact that jq is happy with a concatenation of JSON objects and q is not. For example {'foo':1}{'foo':2} as opposed to [{'foo':1},{'foo':2}]
- davesnx 6y agoSure, it's a missing feature "," creates 2 spins of the filter. I certantly didn't use it, but I see where it's useful, will implement it soon.
- pwm 6y agoTo be fair that is a JSON parse error.
- jeffbee 6y agoYes, but the inputs to jq are not JSON, they are "a sequence of whitespace-separated JSON values which are passed through the provided filter one at a time" which is the relevant thing if you are going to try to replace jq.
- davesnx 6y agoYep, kind of. The comma operations means that the "filters" are duplicated, so instead of one json state you would pass two if there's one coma; and ofcourse any number of commas are allowed.