-
-
Notifications
You must be signed in to change notification settings - Fork 467
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
Reworked get_application_command
behaviour
#1678
Conversation
for more information, see https://pre-commit.ci
ping pong |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #1678 +/- ##
==========================================
- Coverage 33.25% 33.23% -0.02%
==========================================
Files 95 95
Lines 18412 18423 +11
==========================================
Hits 6123 6123
- Misses 12289 12300 +11
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Head branch was pushed to by a user without write access
Summary
type
now defaults toApplicationCommand
, allowing users to get any command type by default instead of justSlashCommand
. While changing defaults without warning could be considered breaking, all command names must already be unique and as such changing the default type would have no effect unless, for some reason, the user was intentionally gettingNone
while using an existing command name.The main addition here is support for qualified command names to easily get subgroups/subcommands, similar to how
get_command
works onext.commands.Bot
. This search occurs if they input a somewhat valid qualified name, only validating if it's all lowercase and exactly two or three words (e.g.group subcommand
orgroup subgroup subcommand
would both be valid.)Closes #1625
Information
examples, ...).
Checklist
type: ignore
comments were used, a comment is also left explaining why.