Clarify that updating the message is optional when ACKing a component interaction #4035
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 tasks
|
Not showing a loading state is probably a client bug, so when you do this it should show a loading state :( |
|
it is documented as not showing a loading state, and it is often used as just an ack, so changing it to show a loading state would be a breaking change and remove functionality; a new response type to show a loading state (or a body param) could be added instead |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unlike acknowledging a slash/context command with DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE which requires a message to be sent later, acknowledging an interaction (button presses etc.) with DEFERRED_UPDATE_MESSAGE does not require that the message is actually updated later.
The current wording is a bit ambiguous and resulted in some questions in the Discord Developer server; adding an "optionally" hopefully makes it clearer that a follow up is not required.