Running command that pipes to another command

Describe the problem

Currently, there is no way via the API to pipe the output of a command into another command. For example to run something similar to:

echo '{"key":"value"}' | jq '.'

Describe your solution

• Work out how to actually pipe one command into another using Process as currently it doesn’t work. Likely the issue relates to the standard out and in being redirected/captured as streams.
• Commands can be a structure rather than just executed immediately as a function like now.
• A Pipeline structure can then be built from a series of Commands and then executed all together with each command piping into the next.

Checklist

• I’ve read the guide for contributing.
• I’ve checked there are no other open pull requests for the feature.
• I’ve checked there are no other open issues for the same feature.

Additional context

It looks like a change may be made with how the command(s) are prepared and built using ProcessBuilder so that they are executed correctly.

Workaround Currently, you can run multiple commands by simply capturing the output of the first command into a Kotlin property and then running the second command using its value as input.

[lordcodes]

I agree. I have created #120 to track the Command abstraction.

[jmfayard]

If the dependency is an issue, we can put the pipeline feature in a separate module.

Also it was fun to discuss but I don’t really need pipelines right now.

Having the Command abstraction on the other hand would be really helpful.

Le jeu. 11 août 2022 à 13:26, Andrew Lord @.***> a écrit :

Maybe I just don’t see it until I would try and work on it, however, there is no threading now and the pipeline would be running the commands sequentially. I don’t see the difference to just running one command at a time in a process like they are now, but that each commands reads in from stream.

Anyway, realistically I’m not going to look into this or work on this anytime soon. If you would like this soon, then you are welcome to work on something. However, I’m really not a fan of introducing that library as a dependency, due to the fact it is a Java library with no recent changes. If threading and a lot of complexity is required to implement this, i.e. it isn’t as simple as it seems to me 🤣, pipelines could be built as a separate library potentially.

— Reply to this email directly, view it on GitHub https://github.com/lordcodes/turtle/issues/104#issuecomment-1211861240, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADQFSH4P76O2A4TYJNXMY3VYTPNVANCNFSM5Z6BSIKQ . You are receiving this because you commented.Message ID: @.***>