4 ms·
I never managed to wrap my head around jq syntax however
by hobo_mark 6y ago
I never managed to wrap my head around jq syntax however
- michaelmior 6y agoI agree it can be a little obtuse at times and I still do occasionally find myself having to consult the documentation despite using it pretty regularly for some time. I do also sometimes make use of gron[0] since it integrates well with standard Unix tools. The pipelines I write with gron are probably pretty brittle in the sense that I expect they might be incorrect for some edge cases. But for some quick exploratory analysis, it's a tool I like to have handy. [0] https://github.com/tomnomnom/gron/ https://github.com/tomnomnom/gron/
- busterarm 6y agoIt takes a while. jq really needs a repl.
- bionhoward 6y agoCheck out ijq...used it this past week to deal with some ugly nested FHIR data. Not perfect, a bit laggy, sometimes crashes your terminal, but really cool in a lot of cases https://sr.ht/~gpanders/ijq/ https://sr.ht/~gpanders/ijq/
- michaelmior 6y agoSeems like you can get something pretty close with fzf. echo '' | fzf --print-query --preview 'jq {q} input.json'
- qbasic_forever 6y agoI'm with you too. I've never found a query language except SQL that has really stuck in my head. Pandas, jq, XSL, etc... it all has me running screaming back to SQL.