Fix Discord component interaction dispatch - #80
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or 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
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.
Summary
Resolve Discord Components V2 channel-select partials through the interaction guild cache, falling back to Discord fetch only when absent. Validate the resolved channel is a standard text channel in the same guild before checking Bill's required permissions and persisting it.
Make the persistent profile button and select DynamicItem templates disjoint while preserving existing custom IDs. The supported-action registry ensures every emitted wizard action has exactly one dispatcher and prevents unknown actions from being generated.
Add focused regressions for real discord.py application-command partials, cache and fetch resolution, rejected channel kinds and guilds, fetch errors, persisted channel IDs, profile select/button dispatcher exclusivity, and action exhaustiveness.
Related work
None.
Checks
Risk and rollout
Low. Existing persistent custom IDs remain compatible. Authorization, stale-revision handling, permission validation, and persistence contracts are unchanged. No deployment or data changes are included.