up VS jid

This fx rewrite is very exciting. I'll have to try it. I thought of fx as a wrapper around jq, that allowed quick iteration over building jq scripts. Sort of an Ultimate Plumber [1] but only for jq. It looks like it is now more like a JavaScript processor plus an interactive viewer.

Someone mention Visidata[2]? VisiData is also a TUI that is great on tabular data, and it can work with json. If your JSON is mostly tabular in nature, Visidata does a great job at showing that data and allowing you to explore it. A lot of json I deal with is tabular-like data. There is a great tutorial [3], that can help you get your bearings with Visidata. Once you understand those basics you might want to look at this thread [4] for what commands you can use with json.

[1] Ultimate Plumber: https://github.com/akavel/up

Ultimate plumber can do this.

https://github.com/akavel/up

Been using up for years but this looks nice too

Fun. But I can achieve the same result (I think) with ultimate plumber and regular jq, but without being restricted just to jq. Feel free to correct me.

Up - The Ultimate Plumber makes the best pipes !

As an alternative allowing the use of any shell command/pipeline on the results interactively, see also: https://github.com/akavel/up

Would https://github.com/akavel/up solve your problem?

It took me a while to grok jq, but now that I do I kinda like it? I don't think I want to learn yet another thing.

I do like tools that complement/supplement jq though, like jid: https://github.com/simeji/jid

Link for the lazy: https://github.com/simeji/jid

If you're trying to work out the structure and content of an API's JSON responses, you can keep paging through the documentation and the paged output of less or you can reach for more precise JSON parsing tools such as, jq and jid.

Yeah, I love me some jq, and my first reaction to the JSON tools page was 'What do these bring to the table that jq doesn't?". Gron and Jid changed my mind.