Expose message_reference.type on MessageReference#311
Merged
KubaZ2 merged 4 commits intoNetCordDev:alphafrom Apr 7, 2026
Merged
Expose message_reference.type on MessageReference#311KubaZ2 merged 4 commits intoNetCordDev:alphafrom
KubaZ2 merged 4 commits intoNetCordDev:alphafrom
Conversation
…ault value of 0 if not provided
|
The documentation preview is available at https://preview.netcord.dev/311. |
KubaZ2
requested changes
Apr 7, 2026
Co-authored-by: Kuba_Z2 <77853483+KubaZ2@users.noreply.github.com>
KubaZ2
requested changes
Apr 7, 2026
Co-authored-by: Kuba_Z2 <77853483+KubaZ2@users.noreply.github.com>
Member
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds support for the type field on message_reference objects returned in message payloads, including MESSAGE_CREATE gateway events and retrieved messages.
Discord documents message_reference.type as optional for now, with unset values treated as the default value (0, Reply) for backward compatibility. To match that behavior, MessageReference.Type now exposes the field and assumes the default when it is missing.
Docs: https://docs.discord.com/developers/resources/message#message-reference-structure