Skip to main content

Should #trurl accept JSON input? If so how? I need your input and feedback on this:

github.com/curl/trurl/pull/311


Add --json-file/-j option to read from file w/ json contents by jacobmealey · Pull Request #311 · curl/trurl

This adds --json-file as an option to read from a file that contains a json representation of the urls. It works very similarly to --url-file. The --json-file input structure is designed to match r...
GitHub
#trurl
in reply to daniel:// stenberg://

Ben Zanin
Ben Zanin
• •

I think... this is something I would prefer to see omitted..? For manipulating JSON input I already have jq(1), and frankly a small library of function definitions in a jq library file would suffice. It adds quite a lot of code to a small, simple tool and offers the mild benefit of naturally extending an input type to accept another format.

(Probably my bias towards unix-y pipelines with composable tools is showing here; this feature might appeal more to cygwin/Windows users.)

in reply to Ben Zanin

daniel:// stenberg://
daniel:// stenberg://
• •
@gnomon that's in the direction I'm leaning towards as well, it's just that we have had quite a few persons asking for something like this...
@Ben Zanin
⇧