-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 field "pending" in Guild Member Update #2567
Comments
The documentation for GUILD_MEMBER_UPDATE says that |
pretty sure it should be required; that's my fault
this seems to be an actual bug |
We're looking into refactoring & improving how pending works right now per feedback from the community. So.... this is a wontfix for now. Stay tuned. @advaith1 is right that this is an actual bug. |
Add #[serde(default)] to the `pending` field on guild member updates. This had to be done as the bug that happens is currently a wontfix from Discord as they work of a better suited replacement. discord/discord-api-docs#2567 (comment) Approved-by: Valdemar Erk <valdemar@erk.io> Approved-by: Jens Reidel <adrian@travitia.xyz> Co-authored-by: Jens Reidel <adrian@travitia.xyz> Signed-off-by: Gautam Abhyankar <gautam.abhyankar@gmail.com>
Closing this as a wontfix per above. |
Description
Some
GUILD_MEMBER_UPDATE
events do not seem to include thepending
field.Steps to reproduce
The
pending
field is missing when any user changes their avatar/profile picture (from my debugging at least)Expected Behavior
The
pending
field should be included as per #2396 (comment)Current Behavior
The
pending
field doesn't get includedLog received from the gateway:
{"t":"GUILD_MEMBER_UPDATE","s":100,"op":0,"d":{"user":{"username":"...","public_flags":64,"id":"331804882837176322","discriminator":"1122","avatar":"a_684331f516e9a0aa3 012ce06eab866a2"},"roles":["665325651728793600"],"mute":false,"joined_at":"2020-11-04T22:53:24.007000+00:00","hoisted_role":"665325651728793600","guild_id":"576325772629901312","deaf":false}}
The text was updated successfully, but these errors were encountered: