-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
refactor!: Remove InteractionResponse
#10689
Conversation
BREAKING CHANGE: `InteractionResponse` has been removed. Create interaction collectors via `with_response` or fetching the reply.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
InteractionResponse
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙏
9bb3b46
to
7fd8540
Compare
7fd8540
to
31f23df
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
We'll probably want to test InteractionCollector
on ephemeral InteractionCallbackResource
messages now that this is fully cleaned up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs some more tests for not passing options 😅
Co-authored-by: Almeida <github@almeidx.dev>
Please describe the changes this PR makes and why it should be merged:
Removing
InteractionResponse
, a class that has brought us many pains and bugs (still present) that are difficult or impossible to fix (we go back and forth sometimes). The existing solution is to simply usewithResponse
, a recent addition to the Discord API, which does not incur an extra API call.Status and versioning classification: