Skip to content
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

Missing interactions permissions field on Kord Core's Member object #664

Closed
MrPowerGamerBR opened this issue Aug 9, 2022 · 0 comments · Fixed by #884
Closed

Missing interactions permissions field on Kord Core's Member object #664

MrPowerGamerBR opened this issue Aug 9, 2022 · 0 comments · Fixed by #884

Comments

@MrPowerGamerBR
Copy link
Contributor

MrPowerGamerBR commented Aug 9, 2022

When you receive a interaction, the member object has a permissions field, which allows you to check what permissions the member has, however this is "thrown away" when creating the MemberData.

It would be nice if there was a Member entity that does expose the permissions field, so you can do permissions checks without needing to do REST calls.

While @lukellmann pointed out that there is GuildInteraction.permissions, having the Member object have the permissions field is also useful for slash command options, because Members retrieved from the resolved objects field in slash commands also have the permissions field.

Example: Let's suppose you have a /user info @LustigerLurch command, and you want to show the permissions' of the provided member in the command, the permissions of the user are provided in the partial member within the resolved.members map. This avoids a REST request to get the roles' permissions.

image

@MrPowerGamerBR MrPowerGamerBR changed the title Missing permissions field on Kord Core's Member object Missing interactions permissions field on Kord Core's Member object Aug 9, 2022
Tmpod added a commit to Tmpod/kord that referenced this issue Oct 13, 2023
Tmpod added a commit to Tmpod/kord that referenced this issue Oct 13, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant