Skip to content
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

Allow non-file arguments to be piped in #1144

Closed
tedivm opened this issue Oct 11, 2018 · 1 comment
Closed

Allow non-file arguments to be piped in #1144

tedivm opened this issue Oct 11, 2018 · 1 comment

Comments

@tedivm
Copy link

tedivm commented Oct 11, 2018

I have a project that has commands that take a single argument, and I would like it if that single argument could be autopopulated with the contents of stdin if something has been piped to the project. Right now it seems like my only option would be to make the argument optional and then if it isn't set check stdin myself, and then display an error if that isn't set.

@davidism
Copy link
Member

This doesn't seem like an appropriate use of pipes. It should be fairly straightforward to implement with a custom Argument class as you described, and I'd rather leave it to projects to do that as needed.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants