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

Client#messageReactionAdd now relies on the GUILD_MEMBER partial #4921

Closed
1 task
monbrey opened this issue Oct 20, 2020 · 0 comments · Fixed by #4922
Closed
1 task

Client#messageReactionAdd now relies on the GUILD_MEMBER partial #4921

monbrey opened this issue Oct 20, 2020 · 0 comments · Fixed by #4922

Comments

@monbrey
Copy link
Member

monbrey commented Oct 20, 2020

Please describe the problem you are having in as much detail as possible:
The changes introduced in #4791 (getUser => getUserFromMember) now requires the GUILD_MEMBER partial in order to emit for uncached Users - in 12.3.1 this was the USER partial.

Include a reproducible code sample here, if possible:

const { Client } = require("discord.js")
const client = new Client({
    partials: ["MESSAGE", "REACTION", "USER"] //failing - add "GUILD_MEMBER" to resolve
});
client.once("ready", () => {
    client.users.cache.clear();
});
client.on("messageReactionAdd", (reaction, user) => {
    console.log(`${user.username} reacted with ${reaction.emoji.name}`);
});
client.login(token);

Further details:

  • discord.js version: 12.4.0
  • Node.js version: 14.7.0
  • Operating system: Windows 10
  • Priority this issue should have – please be realistic and elaborate if possible: medium, workaround available

Relevant client options:

  • partials: ["MESSAGE", "REACTION", "USER"]
  • gateway intents: none
  • other: none
  • I have also tested the issue on latest master, commit hash:
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants