Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: curl --json has landed
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-users <curl-users_at_lists.haxx.se>
Date: Sat, 5 Feb 2022 10:55:04 +0100 (CET)
On Sat, 5 Feb 2022, Alex Bligh wrote:
>> I had to decide how to act when multiple --json options are used
>
> Perhaps send the individual JSON elements as a JSON array?
>
> EG {"a":1} and {"b":2} becomes [{"a":1}, {"b":2}]
>
> That would seem more JSON friendly.
Sure, but that would require that curl would need to parse and "understand"
the data it sends, so it would be MUCH more complicated. I didn't want to go
there with --json.
We save that complication for the discussed possible future imaginary --jp
option.
Date: Sat, 5 Feb 2022 10:55:04 +0100 (CET)
On Sat, 5 Feb 2022, Alex Bligh wrote:
>> I had to decide how to act when multiple --json options are used
>
> Perhaps send the individual JSON elements as a JSON array?
>
> EG {"a":1} and {"b":2} becomes [{"a":1}, {"b":2}]
>
> That would seem more JSON friendly.
Sure, but that would require that curl would need to parse and "understand"
the data it sends, so it would be MUCH more complicated. I didn't want to go
there with --json.
We save that complication for the discussed possible future imaginary --jp
option.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-users Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-02-05