FX: An interactive alternative to jq to process JSON
1–10 of 65 posts
Re: FX: An interactive alternative to jq to process JSON
#2This one has the advantage of being natively understood by aws-cli, meaning you can pass a JMESPath to an AWS call and only receive the filtered / transformed result back.
Re: FX: An interactive alternative to jq to process JSON
#3See https://github.com/simeji/jid/issues/66#issuecomment-4436718...
Re: FX: An interactive alternative to jq to process JSON
#4 fx “code to eval”Re: FX: An interactive alternative to jq to process JSON
#5Apparently, the author wrote this tool because jid was struggling with a 7MB JSON file. See https://github.com/simeji/jid/issues/66#issuecomment-4436718...
- FX "expand/collapse" functionality seems way better for exploring APIs whose shape you don't know
- jid is maybe marginally better for APIs where you have instant recall of the exact shape and need to rapidly query it
Overall, I like FX better because it provides feedback on your query faster.
I am grateful to the author(s) for creating it and I'll be using it instead of JQ whenever I need to wrangle APIs from the CLI.
Re: FX: An interactive alternative to jq to process JSON
#6Re: FX: An interactive alternative to jq to process JSON
#7Re: FX: An interactive alternative to jq to process JSON
#8Re: FX: An interactive alternative to jq to process JSON
#9For example how would you take key k1 from a list of dicts [{k1: v1, k2: v2}, {k1: v3}]?
Re: FX: An interactive alternative to jq to process JSON
#10JQ syntax feels too unusual, doesn't resemble known code, gives me the feeling of looking into cryptic Perl or regex, could never remember the simplest things. For example how would you take key k1 from a list of dicts [{k1: v1, k2: v2}, {k1: v3}]?