fix(commands): some caveats related to guild cache in user app interactions #1262
+39
−3
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
The other remaining part of #1173.
This adds a small note to
Interaction.member
, explaining why role-related fields might not work in certain situations. This was already more or less present onInteraction.guild
, but the internal relationship between those isn't immediately obvious.Also makes the
@commands.dm_only
and@commands.guild_only
checks work properly in all cases by usingguild_id
instead ofguild
for interactions, additionally adding a note linking to the better alternative (iecontexts
).Checklist
pdm lint
pdm pyright