feat: collect workflow inputs via command line#597
Draft
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
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.
Goal
Workflows should allow inputs to be passed via flags and not just JSON. Ex.
Challenges
Clap doesn't really like this, since it mostly expects flags to be defined before parsing.
There are some workarounds in clap-rs/clap#1404, but two notable problems:
apply(Command apply: Argument 'paths' has the same index as 'inputs' and they are both positional arguments\n\n\t UseArg::num_args(1..)to allow one positional argument to take multiple values)Alternative