You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm personally unhappy with the built-in help command in that I can't use h as an alias for it. I know its a small issue and I could just type out the full word help, but to me its a bit irritating, and I'd like to have an option to either make h an alias for it (or anything you want as an alias) or to be able to easily remove the help command and add my own custom one. (the formatter doesn't help because that won't fix the alias issue)
The text was updated successfully, but these errors were encountered:
OoLunar
changed the title
[Feature] Ability to remove help command or at least make so "h" is an alias of the built-in help command
Ability to add aliases to built in commands
Feb 28, 2023
I'm unsure on how we would go about this. Adding aliases through the CommandNextConfiguration class seems obvious, however by default we reference the AliasAttribute when iterating through the commands iirc
We could just add it as a builder type method AddAlias that maps an alias to a command or a command to an alias. Your choice. (Probably simpler to go from alias to command.) It could probably just be a direct "if this alias is in our map, replace it". You could also add it to command handler as a method so that people can register their handlers directly and the handler has the ability to add aliases. I can't think of anything else off the top of my head though.
I'm personally unhappy with the built-in help command in that I can't use h as an alias for it. I know its a small issue and I could just type out the full word help, but to me its a bit irritating, and I'd like to have an option to either make h an alias for it (or anything you want as an alias) or to be able to easily remove the help command and add my own custom one. (the formatter doesn't help because that won't fix the alias issue)
The text was updated successfully, but these errors were encountered: