-
Notifications
You must be signed in to change notification settings - Fork 82
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
Add AutoComplete #435
Add AutoComplete #435
Conversation
0585983
to
441754d
Compare
0346acf
to
f60a193
Compare
@HopeBaron Those classes are in the core module, the file above is rest, so these links don't work |
There is no need for such documentation when you can't refer to it. rest module is unaware of events. This sort of documentation may become invalid since refactoring may now work on those so they will become lies if things change. And Kord has already enough of those kinds of documentation that we should be working on already. |
why "MessageResponding" |
Because these interactions respond with a Message unlike AutoComplete which respond with a Choices object. I think it was @BartArys who suggested MessageResponding |
# Conflicts: # common/src/main/kotlin/entity/Interactions.kt # core/src/main/kotlin/entity/application/ChatInputCommandCommand.kt
not all commands should respond with a message. it may be a command with no message, and chatinput now implements only They are all application commands, it's just that AutoComplete responds diferently, right? |
Okay that was unintended
yes this is why MessageRespondingInteraction is everything but autocomplete, but I am open for better names |
discord/discord-api-docs#3996