Enable flags to be context specific to the subcommand that is using them #524
Assignees
Labels
Feature Enhancement
Enhancing an existing feature driven by business requirements. Typically backwards compatible.
P3
Low priority issue. Will not impact the release schedule if not complete.
Comments
jeromy-cannon
added
P3
|
closing: I think this should already be do-able without any changes needing to be made. All we have to do is create a second flag and make name of the variable different, we can still re-use the same alias and same CLI name, but have different descriptions and different meanings. As long as the two overlapping flags are not used within the same subcommand. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
make it so that flags are subcommand specific, example --private-key is boolean for
solo account getwhereas, string forsolo account create.Note:
I think this should already be do-able without any changes needing to be made. All we have to do is create a second flag and make name of the variable different, we can still re-use the same alias and same CLI name, but have different descriptions and different meanings. As long as the two overlapping flags are not used within the same subcommand.
The text was updated successfully, but these errors were encountered: