feat: deserialize dm/group channels in interactions #1233
Merged
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
Followup to #1012 -
interaction.channel
and other channel fields (slash params, channel select menus, ...) in interactions are now properDMChannel
/GroupChannel
objects in dms/gdms respectively, instead ofPartialMessageable
. They don't have recipient data, since the API doesn't provide the field in interactions.The core addition is this, everything else is primarily documentation/typing adjustments:
disnake/disnake/state.py
Lines 2074 to 2079 in dfaadc6
Checklist
pdm lint
pdm pyright