Add ability to pass scripts via a command line option #152
Conversation
This file contains hidden or 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
|
Nice! |
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.
I've been finding it too cumbersome to keep passing one-off scripts via stdin. Seen as almost all similar Ruby tooling (
ruby,ruby-parse,sorbetare a few examples) support passing inline scripts via an-eoption, I figured that would be a good addition to this tool as well.I implemented the option additively, so that passing in multiple
-eoptions will pass in multiple scripts. Also, in contrast to how Ruby processes-e, I've chosen to process all files and scripts passed via the command-line.