I use all these tools so little that I have to relearn them every single time, making them much less useful to me than they would be otherwise.
yq is a wrapper around jq iirc and has the same syntax, but it do yaml.
Small disclaimer that i think there may be 2 tools known as yq and this is only true of one of them.
I meant tools like jq. I hardly ever use it as it’s hard to use and as a result I forget it making it even harder to use. The same applies to awk, sed, etc. Any tool with a bunch of command line flags and hard to understand arguments and syntax will always be low on my “want to use” list. Ripgrep is a prime example of how to build a command line app that is easy to use every time without trying to remember a billion things.
One of our data providers gives us hundred megabyte json files. Whenever there is a problem with the data they request examples, jq is invaluable in those instances.
yeah, ls | while read file; do echo blabla $file; done
For everything else, there's
yq,xq, andtomlq.I use all these tools so little that I have to relearn them every single time, making them much less useful to me than they would be otherwise.
yq is a wrapper around jq iirc and has the same syntax, but it do yaml.
Small disclaimer that i think there may be 2 tools known as yq and this is only true of one of them.
I meant tools like jq. I hardly ever use it as it’s hard to use and as a result I forget it making it even harder to use. The same applies to awk, sed, etc. Any tool with a bunch of command line flags and hard to understand arguments and syntax will always be low on my “want to use” list. Ripgrep is a prime example of how to build a command line app that is easy to use every time without trying to remember a billion things.
JSON > Yaml
And
jc, apparently: https://programming.dev/post/7063427One of our data providers gives us hundred megabyte json files. Whenever there is a problem with the data they request examples,
jqis invaluable in those instances.yeah,
ls | while read file; do echo blabla $file; done