awesome-jq

Proprietary 'shell' vs. linux DIY/customized setup. There are a multiple publically accessible/usable sources which can be found via search engine(s) to extend bash / unix shell functionality based on points discussed in topic link. few article link topic snippits: * approaches to autocompletion : [0][1] * 'man' command and/or cli option -h to cli command shows 'docstring' / options * jq resources for shell plugin[2] -------------- [0] https://faun.pub/configure-bash-auto-completion-tab-completi... [1] https://tiswww.case.edu/php/chet/readline/rltop.html [2] https://github.com/fiatjaf/awesome-jq

I was searching for an interactive jq editor when I came across this repo [1], which had an intriguing suggestion for a CLI using only fzf: echo '' | fzf --print-query --preview "cat *.json | jq {q}" This sent me down a rabbit hole, and I discovered just how incredibly configurable fzf is. For instance: - `--bind=ctrl-y:execute-silent(jq {q} $tempfile | pbcopy)`: You can bind custom keys to execute non-default behaviors, like copying the current selection or `echo`-ing. - `--query="."`: Start fzf with an initial query (e.g., `.` for jq queries) to streamline the experience. - `--preview-window=top:90%:wrap`: You can configure fzf into different layouts, behaviors, and ANSI colors. - `--header=$'ctrl+y : copy JSON\nctrl+f : copy filter\nenter : output\nesc : exit' \`: fzf supports multi-line header to provide instructions or context fo

You may be interested in an interactive jq tool like jiq or others: https://github.com/fiatjaf/awesome-jq (do a ctrl-f for "interactive" on this page).

Stepping just a little beyond regular ‘loop and filter’ is already difficult without consulting the manual each time — being exacerbated by the impossibility of finding those things in the manual without skimming through most of it. Making an ‘if’ for variations in the input structure is easily a twenty-minute job. Outside of the basic features, Jq's syntax is increasingly arcane and unintuitive—maybe those working with it daily do remember the ‘advanced’ stuff, but I don't. I actually collected a sizable list of alternatives to Jq: https://github.com/TomConlin/json2xpath https://github.com/antonmedv/fx https://github.com/simeji/jid https://github.com/jmespath/jp https://jsonnet.org https://github.com/borkdude/jet https://github.com/jzelinskie/faq https://github.com/dflemstr/rq https://github.com/mgdm/htmlq And there's someone else's list

Shameless plug: https://github.com/fiatjaf/awesome-jq

For everyone pining for a Jq with a different syntax: I have a bunch of links to alternatives collected, you might want to try some of them (some may be for different things than JSON): https://github.com/fiatjaf/awesome-jq https://github.com/TomConlin/json2xpath https://github.com/antonmedv/fx https://github.com/fiatjaf/jiq https://github.com/simeji/jid https://github.com/jmespath/jp https://github.com/cube2222/jql https://jsonnet.org https://github.com/borkdude/jet https://github.com/jzelinskie/faq https://github.com/dflemstr/rq Personally I think that next time I might just fire up Hy and use its functional capabilities.

Shameless plug to my list of interesting `jq` stuff: https://github.com/fiatjaf/awesome-jq It even features a complete rewrite of the actual jq in Go.

Apparently JMESPath is a better JSONPath/dot-notation alternative for querying JSON, while jq and jl are full-featured fully functional programming languages that happen to use JSON as their underlying data type. I had never heard of jl before, but I've recently compiled an "awesome" collection of jq tools, libraries and use-cases at https://github.com/fiatjaf/awesome-jq that may be worth checking out.