feat: support with_response on interaction callbacks
#167
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
TTtie
added
type: enhancement
TTtie
force-pushed
the
feat/interactions-with-response
branch
from
b492198
to
9626977
Compare
this should make the API more consistent with the rest
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.
Separated from #162 as this change is broader.
Adds support for the
with_responseparameter for the interaction callback. This is leveraged:createMessage/editParentcalls to return a fully-fledged Message objectlaunchActivitycalls to return the callback responseNot so sure about including this parameter for other Interaction methods as the usefulness of the data is nearly zero as it is available in user code while performing the interaction.
Ref: discord/discord-api-docs@8bc883c