jp VS jaq

I have a hard time suggesting such a thing, because I find JMESPath incredibly inferior to jq's expressiveness, but if you're in the AWS ecosystem much, you may enjoy https://github.com/jmespath/jp#readme which uses the same query language as does awscli (https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-f...). That may at least pay more dividends than keeping jq's language in your head where it will only ever be used by jq

Have you tried this utility instead: https://github.com/jmespath/jp

There’s also jp, which interprets JMESPath: https://github.com/jmespath/jp

This 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.

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