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.

Sign up for GitHub

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

Jump to bottom

Modifying a CommandSpec's aliases if it's already a subcommand #1528

Closed
rgoldberg opened this issue Dec 23, 2021 · 0 comments · Fixed by #1529
Closed

Modifying a CommandSpec's aliases if it's already a subcommand #1528

rgoldberg opened this issue Dec 23, 2021 · 0 comments · Fixed by #1529
Labels
type: bug 🐛
Milestone
4.6.3

Comments

@rgoldberg
Copy link
Contributor

Currently, if CommandSpec#aliases(String...) is called to modify the aliases of a CommandSpec that is already registered as a subcommand of another CommandSpec, then the aliases registered in the parent are not updated.

The aliases in the parent should be updated to a) keep things consistent, and b) allow aliases to be modified.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug 🐛
Projects
None yet
Milestone
4.6.3
Development

Successfully merging a pull request may close this issue.

Allow aliases of a CommandSpec that is already a subcommand to be properly & consistently modified.
2 participants
@rgoldberg @remkop