Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

first-class support for subcommands #41

Open
HeladoDeBrownie opened this issue Oct 7, 2022 · 0 comments
Open

first-class support for subcommands #41

HeladoDeBrownie opened this issue Oct 7, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@HeladoDeBrownie
Copy link
Member

although there can be many usage strings for a given command, they are all required to route to the same run function. for commands with a large number of usages, it can be confusing to separate out all the cases, which are in practice going to be handled by an if statement regardless, even if they have some shared logic. this can be handled better. try designing it so that each usage can route to its own function

@HeladoDeBrownie HeladoDeBrownie added the enhancement New feature or request label Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant