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
[V3 Alias] Parameterized and fixed-argument command aliases #2011
Comments
I like the suggestion, I've always wanted to write this cog, and have never got around to it. However, I want us to be careful, since as it stands alias is quite a simple cog and I'd like to keep it that way on the front-end - adding these extra features should aim to avoid overwhelming the user with lots of options. Perhaps adding an extra |
Though it would have to have a per-alias toggle to prevent potentially changing behavior on old aliases, I'm opposed in principle to mixing command groups and normal commands. I would keep it under Perhaps a toggle is all that would be needed, if the syntax can be self-describing. Consider:
The first alias parameter is required, since it has no default. The second alias parameter ( |
wew, this one fell threw the cracks. Merged a long time ago |
Or I can misread this, sorry that was CC which fully handles this already. |
Didn't #2455 add this functionality? |
I thought that didn't handle default values for alias, but I'm not the largest alias user, did I miss something with that? |
Ah, sorry, no it doesn't. I didn't see that comment further down. Worth noting that CC doesn't handle default arguments either. |
Feature request
Select the type of feature you are requesting:
Describe your requested feature
I've been in the situation where I or other users want to create shortcuts for long commands with parameters in the middle of those commands, instead of at the end. On the other hand, I've also wanted to prevent any parameters from being added to the end of the aliased command. The Alias cog is the right place to add both.
I wouldn't mind doing this, but it should be fairly simple to put together. I also don't want to start another thing unless it's wanted in core.
What it would probably involve:
Update
At the current moment, it seems as though some of what was requested by this issue has been addressed in #2455. However, Alias still does not support adding defaults to custom parameters.
The text was updated successfully, but these errors were encountered: