feat: support reading from stdin if no path or text is provided #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ovided This update adds flexibility to the clipper tool by allowing it to read input from stdin if neither a file path nor direct text is provided. Changes: - Added support for reading from stdin when no file path or direct text is provided. - Updated usage instructions to reflect the new behavior. This enhancement enables users to use clipper more intuitively in pipelines or scenarios where reading from stdin is preferred.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update adds flexibility to the clipper tool by allowing it to read input from stdin if neither a file path nor direct text is provided.
Changes:
This enhancement enables users to use clipper more intuitively in pipelines or scenarios where reading from stdin is preferred.