-
-
Notifications
You must be signed in to change notification settings - Fork 170
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
Added user_id to message_reaction_add_t #1376
Conversation
✅ Deploy Preview for dpp-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
message_reaction_add_t has reacting_user, which contains an id attribute. This is filled if you have the guild members intent. Is this not filled for you? If there is no member, then you should fill the reacting_user.id with the received user_id, instead of creating a new attribute, this way it works in all situations. See: https://discord.com/developers/docs/events/gateway-events#message-reaction-add |
It doesn't get filled for me, even with the guild members intent. |
Updated test code
|
Adds an user_id field to message_reaction_add_t.
When we get the callback from adding a reaction in a DM, the payload is as follows:
This has no member or user information to fill the corresponding classes, making it impossible to get the user_id of the user that reacted.
Test code:
Code change checklist