The time might come when we add some JSON specific command line options

Re:The time might come when we add some JSON specific comman... by masklinn on Thursday January 20, 2022 @01:44PM (#30012858)

> Hmm… any actual use cases of this?

... interacting with APIs using cURL?

> I don’t find curl —jp a=b to be better than directly sending a payload on a HTTP resource

Getting JSON syntax right, error free, by hand, in a terminal, is not easy. The current equivalent of an eventual `curl --jp a=b` is

    curl -s -H "Content-Type: application/json" --data '{"a":"b"}'

that's a lot of opportunities for getting it wrong.

[ Parent | on HN ]

Re:The time might come when we add some JSON specific comman... by ChrisOstler on Thursday January 20, 2022 @01:50PM (#30012940)

And even more when the JSON is dynamic, and not static: curl -jp a="$B"

[ Parent | on HN ]

Re:The time might come when we add some JSON specific comman... by naikrovek on Thursday January 20, 2022 @02:08PM (#30013179)

> Getting JSON syntax right, error free, by hand, in a terminal, is not easy.

you are right and I wonder why shells haven't done anything to address this. Fish might, actually. colorization isn't really useful in aiding comprehension, but colorization is good at giving an indicator that there is a parse error somewhere.

[ Parent | on HN ]

Re:The time might come when we add some JSON specific comman... by 8n4vidtmkvmk on Thursday January 20, 2022 @01:51PM (#30012959)

its also pretty trivial to alias/wrap that tho

[ Parent | on HN ]