Documentation for Guild Join Requests, aka Server Member Applications - #8531
Documentation for Guild Join Requests, aka Server Member Applications#8531colinloretz wants to merge 7 commits into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
| | Value | Description | | ||
| |-----------|------------------------------------------------------------------| | ||
| | STARTED | applicant started but has not yet submitted their join request | | ||
| | SUBMITTED | applicant submitted their join request, which is awaiting review | | ||
| | APPROVED | join request was approved | | ||
| | REJECTED | join request was rejected | |
There was a problem hiding this comment.
This goes against the current structure of using numeric enums to represent values like these...
There was a problem hiding this comment.
since this feature was made during the clan alpha (and even earlier, back in old DMD days, with earlier versions of member applications), it always used this. I'd assume that it's too much of a breaking change to change that now.
But maybe we could get a compability field?
| | Value | Description | | ||
| |-----------------|--------------------------------------------------------------| | ||
| | TERMS | field requiring the applicant to acknowledge a list of terms | | ||
| | TEXT_INPUT | short text input field | | ||
| | PARAGRAPH | long-form text input field | | ||
| | MULTIPLE_CHOICE | field where the applicant selects one of many options | |
There was a problem hiding this comment.
Ditto, I would've assumed this would follow a shape similar to message components (numeric values, not strings)
colinloretz
changed the title
| #### Guild Join Request Create | ||
|
|
||
| <Warning> | ||
| If using [Gateway Intents](/developers/events/gateway#gateway-intents), the `GUILD_MODERATION` intent will be required to receive this event. |
There was a problem hiding this comment.
The "If" part here is inconsistent with intents declared elsewhere:
discord-api-docs/developers/change-log.mdx
Line 533 in f36e7ca
discord-api-docs/developers/resources/guild.mdx
Lines 985 to 987 in f36e7ca
The documentation is written for API v10 in mind, no?
4 participants
Adding docs for Guild Join Request Endpoints:
Guild Join Request Gateway events:
These endpoints and events require the
KICK_MEMBERSpermission, and the guild must have both theMEMBER_VERIFICATION_GATE_ENABLEDandMEMBER_VERIFICATION_MANUAL_APPROVAL.