You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Um, it doesn't stall per say. Rather it waits for input which can come from stdin. It allows me to type a list of strings (even though it's not something I would do).
I imagine it to be like any of the Linux command utilities, for example cat that when invoked without a file wait for the input to arrive. It allows piping I think rather than allowing an explicit file which might not be mounted in a container.
Of course, I can always refactor it. What do you think?
We want our scripts to be self-documenting, especially in this context of a sub command for which there are many with similar names. Our workflow here is very far from that of core unix tools. 99% of the time, we'll have a file on filesystem to work from. We should work toward that use case first
When the script is called without any argument, there is no output and the process stalls forever.
If there is no stdin upon start, we should assume it was not piped and show an error
The text was updated successfully, but these errors were encountered: