-
Notifications
You must be signed in to change notification settings - Fork 812
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
Unknown Message Component Type 16 #1562
Comments
Looks like metadata for an Activity Card, part of the Recent Activity beta |
@glotchimo if that's the case then it is breaking the marshaling. Should we change the marshaling to be more robust to this? @bwmarrin @FedorLap2006 |
Without documentation (not sure if these have been written/posted by Discord yet, all we have is the known 8 here), it's hard to say what that would look like here. Also, considering how much higher it is than the current max type of 8, has me wondering if it's temporary or if there are 8+ more message component types on the way? Lines 8 to 21 in 41a66e5
|
Either way, marshaling ceases completely when an unexpected field is encountered. Seeing as how this can and actually is happening, I believe we should not completely cease marshaling when this happens. |
I received a Message Create message that is unable to be unmarshalled because it has a Message Component of type 16.
Here is the components field of the message create with identifying information censored
This component prevents the entire message from being unmarshalled because we do an early return if we receive a message component whose type is not handled:
// UnmarshalJSON is a helper function to unmarshal MessageComponent object.
The text was updated successfully, but these errors were encountered: