-
Notifications
You must be signed in to change notification settings - Fork 17
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
Deeply Nested Subcommand Scripts #28
Labels
Feature
New feature or request for major functionality changes
Comments
Nekroze
added a commit
that referenced
this issue
Sep 27, 2018
A new way to define and manage subcommands, should also be more uniform. Fixes issue #28
Nekroze
added a commit
that referenced
this issue
Sep 27, 2018
A new way to define and manage subcommands, should also be more uniform. Fixes issue #28
Nekroze
added a commit
that referenced
this issue
Sep 27, 2018
A new way to define and manage subcommands, should also be more uniform. Fixes issue #28
Nekroze
added a commit
that referenced
this issue
Sep 27, 2018
A new way to define and manage subcommands, should also be more uniform. Fixes issue #28
Nekroze
added a commit
that referenced
this issue
Sep 27, 2018
A new way to define and manage subcommands, should also be more uniform. Fixes issue #28
Nekroze
added a commit
that referenced
this issue
Sep 27, 2018
A new way to define and manage subcommands, should also be more uniform. Fixes issue #28
Nekroze
added a commit
that referenced
this issue
Sep 30, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently subcommands are scripts in a single directory even though there are now many nested subcommands, this has made the scripts bloated and hard to grok/read/refactor.
Describe the solution you'd like
Allow directories under
app/subcommands
to become subcommand namespaces likedab repo
is that does nothing but provide info and access to other subcommands represented by scripts in that directory.Continuing with the repo example,
app/subcommands/repo.sh
would become something likeapp/subcommands/repo/{entrypoint,group,manage}.sh
which would require the currentrepo add
top level repo sub subcommands to be moved to something like manage.Describe alternatives you've considered
Could rewrite in a different language that allows better composition, too big of an increment though.
Additional context
N/A.
The text was updated successfully, but these errors were encountered: