docs: add notes about MESSAGE_CONTENT intent in affected data fields
#556
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Jiralite
reviewed
Aug 6, 2022
SpaceEEC
approved these changes
Aug 6, 2022
Jiralite
requested changes
Aug 6, 2022
There was a problem hiding this comment.
MESSAGE_CONTENT(1 << 15) will be a privileged intent for verified apps,- this intent is required to receive a non-empty value from this field
I honestly think this doesn't flow smoothly and still doesn't quite make sense for version 10. For version 10, this is already in effect. This isn't a will be, it already is.
For version 10, I would recommend something like this:
The
MESSAGE_CONTENT(1 << 15) privileged gateway intent is required for verified applications to receive a non-empty value from this field
For versions before this, I recommend something like this:
The
MESSAGE_CONTENT(1 << 15) privileged gateway intent will become required [date here] for verified applications to receive a non-empty value from this field
kyranet
approved these changes
Aug 7, 2022
vladfrangu
requested changes
Aug 7, 2022
Jiralite
reviewed
Aug 10, 2022
vladfrangu
approved these changes
Aug 10, 2022
MESSAGE_CONTENT intent in affected data fieldsMESSAGE_CONTENT intent in affected data fields
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please describe the changes this PR makes and why it should be merged:
Adds notes about the
MESSAGE_CONTENTintent, which will be privileged for verified apps after August 31, 2022.There are affected fields in
APIMessage, which arecontent,embeds,attachments, andcomponents.If applicable, please reference Discord API Docs PRs or commits that influenced this PR: