3 ms·
Yeah, I've always liked the idea of jq but personally I find it easier to open a REPL in the language I'm most familiar with (which happens to be JS, which does
by brundolf 3y ago
Yeah, I've always liked the idea of jq but personally I find it easier to open a REPL in the language I'm most familiar with (which happens to be JS, which does make a difference) and just paste in the JSON and work with it there
It may be more verbose, but I never have to google anything, which makes a bigger difference in my experience
- wwader 3y agohttps://github.com/wader/fq https://github.com/wader/fq has a REPL and can read JSON. Tip is to use "paste | from_json | repl" in a REPl to paste JSON into a sub-REPL, you can also use `<text here>` with fq which is a raw string literal
- brundolf 3y agoThe important part wasn't having a REPL, it was using a language I already know off the top of my head
- Too 3y agoYes. So much easier to reuse other common helper functions. Once you’ve finished exploration you can just copy the code into production instead of translating.