it also doesn't even require JSON input, meaning one could use it strictly for composing valid output JSON:
# where -n = null input
jq -n --arg foo bar '{"meet me": ("at the "+$foo)}'
I use it for transforming AWS responses all the time. I put jq up there with vim as one of the "must have" tools. In fact, the keys `%!jq .` are burned into my fingers because I type them a lot
_ed: fixed a mobile character replacement, added in the --arg flag I couldn't remember at the time_
Comments
I guess that depends on one's definition of transformation but:
it also doesn't even require JSON input, meaning one could use it strictly for composing valid output JSON: I use it for transforming AWS responses all the time. I put jq up there with vim as one of the "must have" tools. In fact, the keys `%!jq .` are burned into my fingers because I type them a lot_ed: fixed a mobile character replacement, added in the --arg flag I couldn't remember at the time_