json_to_paths VS jaq

as a list of jq arguments.

You can use it to make queries or keep track of a documents structure.

https://github.com/TomConlin/json_to_paths

b) may care when the structure (but not the values) change.

so a jq utility[] that spits out all the jq paths for a json files helps in both cases.

[] https://github.com/TomConlin/json_to_paths

https://github.com/01mf02/jaq/blob/main/Cargo.lock

That's a lot of dependencies..

Thanks for the jqjq shoutout! :) i'm quite sure jq is turing complete, jq (and jqjq!) can implement brainfuck https://github.com/01mf02/jaq/blob/main/examples/bf.jq

/uj Because of this post, I have learned I could have been using jaq instead of jq.

There's also jaq which is written in Rust, aims for compatibility with jq (except some specific features), and boasts better performance.

jaq is closer to that

if [[ $(hyprctl -j getoption general:layout | jaq -r '.str') = "master" ]]; then hyprctl keyword general:layout "dwindle" else hyprctl keyword general:layout "master" fi you'll need https://github.com/01mf02/jaq

You will need https://github.com/01mf02/jaq

I've been getting a lot of mileage out of https://github.com/itchyny/gojq#readme recently due to two things: its vastly superior error messages and the (regrettably verbose) `--yaml-input` option

I also have https://github.com/01mf02/jaq#readme installed but just haven't needed it