add clarifications in permissions docs #7332
Merged
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
donaldchen
requested review from
JustinBeckwith
and removed request for
a team
Contributor
I think every permission that applies to text-in-voice has V for voice now? |
Author
Oh I see. In that case, I think I can make a mapping from T to channel types that is consistent for every permission then |
advaith1
reviewed
Jan 6, 2025
Co-authored-by: advaith <[email protected]>
shaydewael
approved these changes
Jan 7, 2025
mazylol
pushed a commit
to mazylol/discord-api-docs
that referenced
this pull request
Jul 3, 2025
* add descriptions for channel types * update ADD_REACTIONS and USE_EMBEDDED_ACTIVITIES table entries * npm run fix:tables * fix table * add channel type mapping * Update docs/topics/Permissions.md Co-authored-by: advaith <[email protected]> --------- Co-authored-by: advaith <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This PR adds the docs clarifications requested from #7318 .
A few notes:
CREATE_GUILD_EXPRESSIONSandCREATE_EVENTSpermissions are still not publicI unabbreviated T, V, and S in a new table, but I didn't map them to every channel type because the mapping is different based on the permission. For example,Tapplies toGUILD_VOICE(for its associated text chat) for a permission likeSEND_MESSAGES, but it doesn't apply toGUILD_VOICEfor a permission likeCREATE_PUBLIC_THREADS