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

PermissionOverwrite.type is a number when a overwrite is deleted in the oldChannel from Client#channelUpdate #6096

Closed
Jarco-dev opened this issue Jul 11, 2021 · 0 comments · Fixed by #6092

Comments

@Jarco-dev
Copy link

Please describe the problem you are having in as much detail as possible:
When deleting a permission ovewrrite from a channel the oldChannel keeps the permissionOverwrite type as a number (0 for role 1 for member)

Include a reproducible code sample here, if possible:

  • Delete a permission overwrite to show the bug
client.on("channelUpdate", (oldChannel, newChannel) => {
    console.log(oldChannel.permissionOverwrites.cache.first()?.type, newChannel.permissionOverwrites.cache.first()?.type)
});

Further details:

  • discord.js version: v13
  • Node.js version: v14.16.0
  • Operating system: Windows 10
  • Priority this issue should have – please be realistic and elaborate if possible: medium

Relevant client options:

  • partials: none

  • gateway intents: GUILDS

  • other: none

  • I have also tested the issue on latest master, commit hash: discord.js@13.0.0-dev.d433fe8.1625961832

@Jarco-dev Jarco-dev changed the title PermissionOverwrite.type is 0 when a overwrite is deleted in the oldChannel from Client#channelUpdate PermissionOverwrite.type is a number when a overwrite is deleted in the oldChannel from Client#channelUpdate Jul 11, 2021
@iCrawl iCrawl linked a pull request Jul 12, 2021 that will close this issue
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 30, 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.

1 participant