fx: Command-line JSON processing tool - https://github.com/antonmedv/fx
dasel: JSON, YAML, TOML, XML, and CSV query and modification tool - https://github.com/TomWright/dasel
dsq: CLI tool for running SQL queries against JSON, CSV, Excel, Parquet, and more - https://github.com/multiprocessio/dsq
gron: Make JSON greppable - https://github.com/tomnomnom/gron
jello: Filter JSON and JSON Lines data with Python syntax - https://github.com/kellyjonbrazil/jello
jless: Command-line pager for JSON data - https://github.com/PaulJuliusMartinez/jless
jid: Json incremental digger - https://github.com/simeji/jid
jql: JSON query language CLI tool - https://github.com/yamafaktory/jql
qp: Command-line (ND)JSON querying - https://github.com/paybase/qp
If I'm trying to understand some new json data, I start with visidata, and then I poke around to find the data I want. If it is data I want to extract again, I use jq to get the interesting bits. Sometimes I use that in combination with sqlite-utils to store that data so I can query it. (I haven't tried some of the other tools that will create a sqlite database for you.)
- https://github.com/saulpw/visidata - https://github.com/simonw/sqlite-utils
I've used Visual Studio before, and one thing that annoys me about VS Code is that I can't just drag a tab out to a new window and have it be connected to the same project or session or whatever.
Even if one uses "new window" and moves the tab, things occur such as it not picking up imports, etc.
For GNOME-Builder, if I want to debug LSP-issues, I add "--env=JSONRPC_DEBUG=1" to the commandline and I get nice output. For VSCode? - No idea. In the end I redirected strace for writes to a file and then grepped for "Content-Length", because I was frustrated that there was no straightforward way to do this otherwise.
Another issue I have with VSCode is, that it adds some folders to the project, that's something I absolutely can't stand.
or you could write a small javascript and run it via node
Honestly it’s hard to beat text formats for viewing JSON unless you have particular queries. There’s just a lot of data no matter which way you try to represent it