-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] allow JSON input in the same form as JSON parts output #263
Comments
This is a request that has been brought up a couple of times. #176 (comment) the last one I could find was issue 176 where bagder recommended tabling a request for this feature unless others were interested in it. I do think it could be a helpful feature, but we would need to add a json parsing library (which might provide an opportunity to clean up the current json code). It would be a good bit of work but would be a nice addition to trurl because I suspect we will keep getting requests for this as time goes on. |
Agreed, it seems like a feature people will keep suggesting, meaning that there probably is merit to the idea. |
I've started looking into getting this working. it looks like json-c is a pretty popular library for this, so i've been using that. I think it makes sense for the json input to be compatible with the json output, so it right now it is an array of objects with one entry ( With this, the most basic json input is I'm not sure how it should work from a user standpoint. it would be nice if it could all be wrapped up in Edit: |
We have decided to not do JSON input. At least not until there is a common/standard JSON URL object that we would support. |
the current output JSON feature
would be useful to be able to reverse this operation
it could be used with HEREDOC, files and pipes
For example example (I am sure someone could come up with better args)
with files and pipes
and plain text list of urls
or may be it makes sense to build a separate url builder tool to accompany turl?
The text was updated successfully, but these errors were encountered: