From 941d359d9a7a6527de460198c4fa586634aa5fe2 Mon Sep 17 00:00:00 2001 From: b3ssel Date: Wed, 23 Apr 2025 16:59:45 +0200 Subject: [PATCH 1/7] docs: update allowed mentions object section Updated the section with the new components v2 behaviour. --- docs/resources/message.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/resources/message.mdx b/docs/resources/message.mdx index a8d912371c..ce1216d9e1 100644 --- a/docs/resources/message.mdx +++ b/docs/resources/message.mdx @@ -625,7 +625,7 @@ For the `attachments` array in Message Create/Edit requests, only the `id` is re ### Allowed Mentions Object -The allowed mention field allows for more granular control over mentions without various hacks to the message content. This will always validate against message content to avoid phantom pings (e.g. to ping everyone, you must still have `@everyone` in the message content), and check against user/bot permissions. +The allowed mention field allows for more granular control over mentions without various hacks to the message content. This will always validate against message content or [message component](docs/components/using-message-components) content to avoid phantom pings (e.g. to ping everyone, you must still have `@everyone` in the message content or message component content), and check against user/bot permissions. ###### Allowed Mention Types @@ -648,7 +648,7 @@ The allowed mention field allows for more granular control over mentions without Due to the complexity of possibilities, we have included a set of examples and behavior for the allowed mentions field. -If `allowed_mentions` is _not_ passed in (i.e. the key does not exist), the mentions will be parsed via the content. This corresponds with existing behavior. +If `allowed_mentions` is _not_ passed in (i.e. the key does not exist), the mentions will be parsed via the message content or message component content. This corresponds with existing behavior. In the example below we would ping @here (and also @role124 and @user123) @@ -711,7 +711,7 @@ Due to possible ambiguities, not all configurations are valid. An _invalid_ conf Because `parse: ["users"]` and `users: [123, 124]` are both present, we would throw a validation error. This is because the conditions cannot be fulfilled simultaneously (they are mutually exclusive). -Any entities with an ID included in the list of IDs can be mentioned. Note that the IDs of entities not present in the message's content will simply be ignored. +Any entities with an ID included in the list of IDs can be mentioned. Note that the IDs of entities not present in the message content or message component content will simply be ignored. e.g. The following example is valid, and would mention user 123, but _not_ user 125 since there is no mention of user 125 in the content. From e1fe8008430feac7200a589bed02c18490ce535d Mon Sep 17 00:00:00 2001 From: b3ssel Date: Thu, 24 Apr 2025 00:05:33 +0200 Subject: [PATCH 2/7] docs: update create message and edit message section Updated both sections with the new components v2 behaviour. --- docs/resources/message.mdx | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/resources/message.mdx b/docs/resources/message.mdx index ce1216d9e1..a742664d13 100644 --- a/docs/resources/message.mdx +++ b/docs/resources/message.mdx @@ -806,12 +806,14 @@ When creating a message, apps must provide a value for **at least one of** `cont | files[n]?\* | file contents | Contents of the file being sent. See [Uploading Files](/docs/reference#uploading-files) | | payload_json? | string | JSON-encoded body of non-file params, only for `multipart/form-data` requests. See [Uploading Files](/docs/reference#uploading-files) | | attachments? | array of partial [attachment](/docs/resources/message#attachment-object) objects | Attachment objects with filename and description. See [Uploading Files](/docs/reference#uploading-files) | -| flags? | integer | [Message flags](/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (only `SUPPRESS_EMBEDS` and `SUPPRESS_NOTIFICATIONS` can be set) | +| flags?\*\* | integer | [Message flags](/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (only `SUPPRESS_EMBEDS`, `SUPPRESS_NOTIFICATIONS` and `IS_COMPONENTS_V2` can be set) | | enforce_nonce? | boolean | If true and nonce is present, it will be checked for uniqueness in the past few minutes. If another message was created by the same author with the same nonce, that message will be returned and no new message will be created. | | poll? | [poll](/docs/resources/poll#poll-create-request-object) request object | A poll! | \* At least one of `content`, `embeds`, `sticker_ids`, `components`, `files[n]`, or `poll` is required. +\*\* When the flag `IS_COMPONENTS_V2` is set, the message can only contain `components`. Providing `content`, `embeds`, `sticker_ids`, `files[n]`, or `poll` will fail with a 400 BAD REQUEST response. + ###### Example Request Body (application/json) ```json @@ -887,9 +889,9 @@ The `emoji` must be [URL Encoded](https://en.wikipedia.org/wiki/Percent-encoding ## Edit Message /channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object) -Edit a previously sent message. The fields `content`, `embeds`, and `flags` can be edited by the original message author. Other users can only edit `flags` and only if they have the `MANAGE_MESSAGES` permission in the corresponding channel. When specifying flags, ensure to include all previously set flags/bits in addition to ones that you are modifying. Only `flags` documented in the table below may be modified by users (unsupported flag changes are currently ignored without error). +Edit a previously sent message. The fields `content`, `embeds`, `flags` and `components` can be edited by the original message author. Other users can only edit `flags` and only if they have the `MANAGE_MESSAGES` permission in the corresponding channel. When specifying flags, ensure to include all previously set flags/bits in addition to ones that you are modifying. Only `flags` documented in the table below may be modified by users (unsupported flag changes are currently ignored without error). -When the `content` field is edited, the `mentions` array in the message object will be reconstructed from scratch based on the new content. The `allowed_mentions` field of the edit request controls how this happens. If there is no explicit `allowed_mentions` in the edit request, the content will be parsed with _default_ allowances, that is, without regard to whether or not an `allowed_mentions` was present in the request that originally created the message. +When the `content` field is edited, the arrays `mentions` and `mention_roles` and the boolean `mention_everyone` in the message object will be reconstructed from scratch based on the new content. When the message flag `IS_COMPONENTS_V2` is set, the reconstructed arrays and boolean are based on the edited content in the `components` array. The `allowed_mentions` field of the edit request controls how this happens. If there is no explicit `allowed_mentions` in the edit request, the content will be parsed with _default_ allowances, that is, without regard to whether or not an `allowed_mentions` was present in the request that originally created the message. Returns a [message](/docs/resources/message#message-object) object. Fires a [Message Update](/docs/events/gateway-events#message-update) Gateway event. @@ -910,13 +912,15 @@ All parameters to this endpoint are optional and nullable. |------------------|---------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| | content | string | Message contents (up to 2000 characters) | | embeds | array of [embed](/docs/resources/message#embed-object) objects | Up to 10 `rich` embeds (up to 6000 characters) | -| flags | integer | Edit the [flags](/docs/resources/message#message-object-message-flags) of a message (only `SUPPRESS_EMBEDS` can currently be set/unset) | +| flags | integer | Edit the [flags](/docs/resources/message#message-object-message-flags) of a message (`SUPPRESS_EMBEDS` and `IS_COMPONENTS_V2` only)\*\* | | allowed_mentions | [allowed mention object](/docs/resources/message#allowed-mentions-object) | Allowed mentions for the message | | components | array of [message component](/docs/components/reference#component-object) | Components to include with the message | | files[n] | file contents | Contents of the file being sent/edited. See [Uploading Files](/docs/reference#uploading-files) | | payload_json | string | JSON-encoded body of non-file params (multipart/form-data only). See [Uploading Files](/docs/reference#uploading-files) | | attachments | array of [attachment](/docs/resources/message#attachment-object) objects | Attached files to keep and possible descriptions for new files. See [Uploading Files](/docs/reference#uploading-files) | +\*\* The `SUPPRESS_EMBEDS` flag can be both set and unset, while the `IS_COMPONENTS_V2` flag can only be set. When the `IS_COMPONENTS_V2` flag is set, any of the used `content`, `embeds`, `sticker_ids`, `files[n]`, or `poll` values in the initial message must be set to `null` first, otherwise it will fail with a 400 BAD REQUEST response. + ## Delete Message /channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object) From 8549d8327878730833742ce6b65f51fb367bd88e Mon Sep 17 00:00:00 2001 From: b3ssel Date: Thu, 24 Apr 2025 00:14:44 +0200 Subject: [PATCH 3/7] docs: update sending a message with a component section Added a warning alert box to make users aware of the "IS_COMPONENTS_V2" message flag being irreversible when set to a message. --- docs/components/using-message-components.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/components/using-message-components.mdx b/docs/components/using-message-components.mdx index 6cf26fc671..81bef4915d 100644 --- a/docs/components/using-message-components.mdx +++ b/docs/components/using-message-components.mdx @@ -24,6 +24,10 @@ If you are sending components as part of a [webhook](/docs/resources/webhook) yo To send a message with a component, you need to set the `IS_COMPONENTS_V2` flag (`1<<15`) in your message's `flags` field. This can be done when using [Message Create](/docs/resources/message#create-message), [Execute Webhook](/docs/resources/webhook#execute-webhook), or [responding to an interaction](/docs/interactions/receiving-and-responding#create-followup-message). +:::warn +Setting the `IS_COMPONENTS_V2` message flag cannot be reverted: once the message has been sent, the flag cannot be removed from the message when editing the message. +::: + This flag indicates that the message contains components and disables traditional content and embeds. All content must be sent as components instead of using the standard message format. @@ -103,4 +107,4 @@ See the [list of supported component types](/docs/components/reference#component You can use this information to respond to the interaction, update the message, or perform other actions, such as displaying a modal based on the user's input. -Check out the [Interactions documentation](/docs/interactions/overview) for more information on handling interactions and responding to user input from interactive components. \ No newline at end of file +Check out the [Interactions documentation](/docs/interactions/overview) for more information on handling interactions and responding to user input from interactive components. From fbbbbf38dc4cdfc6ed69b763a81ca28a527a36bb Mon Sep 17 00:00:00 2001 From: b3ssel Date: Thu, 24 Apr 2025 11:41:33 +0200 Subject: [PATCH 4/7] docs: update execute webhook and edit webhook message section Updated both desction with the new components v2 behaviour. --- docs/resources/webhook.mdx | 65 ++++++++++++++++++++------------------ 1 file changed, 35 insertions(+), 30 deletions(-) diff --git a/docs/resources/webhook.mdx b/docs/resources/webhook.mdx index 98c51c435b..76771a51fd 100644 --- a/docs/resources/webhook.mdx +++ b/docs/resources/webhook.mdx @@ -220,27 +220,29 @@ Discord may strip certain characters from message content, like invalid unicode ###### JSON/Form Params -| Field | Type | Description | Required | -|-------------------|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| -| content | string | the message contents (up to 2000 characters) | one of content, file, embeds, poll | -| username | string | override the default username of the webhook | false | -| avatar_url | string | override the default avatar of the webhook | false | -| tts | boolean | true if this is a TTS message | false | -| embeds | array of up to 10 [embed](/docs/resources/message#embed-object) objects | embedded `rich` content | one of content, file, embeds, poll | -| allowed_mentions | [allowed mention object](/docs/resources/message#allowed-mentions-object) | allowed mentions for the message | false | -| components \* | array of [message component](/docs/components/reference#component-object) | the components to include with the message | false | -| files[n] \*\* | file contents | the contents of the file being sent | one of content, file, embeds, poll | -| payload_json \*\* | string | JSON encoded body of non-file params | `multipart/form-data` only | -| attachments \*\* | array of partial [attachment](/docs/resources/message#attachment-object) objects | attachment objects with filename and description | false | -| flags | integer | [message flags](/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (only `SUPPRESS_EMBEDS` and `SUPPRESS_NOTIFICATIONS` can be set) | false | -| thread_name | string | name of thread to create (requires the webhook channel to be a forum or media channel) | false | -| applied_tags | array of snowflakes | array of tag ids to apply to the thread (requires the webhook channel to be a forum or media channel) | false | -| poll | [poll](/docs/resources/poll#poll-create-request-object) request object | A poll! | one of content, file, embeds, poll | +| Field | Type | Description | Required | +|-------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| content | string | the message contents (up to 2000 characters) | one of content, file, embeds, poll | +| username | string | override the default username of the webhook | false | +| avatar_url | string | override the default avatar of the webhook | false | +| tts | boolean | true if this is a TTS message | false | +| embeds | array of up to 10 [embed](/docs/resources/message#embed-object) objects | embedded `rich` content | one of content, file, embeds, poll | +| allowed_mentions | [allowed mention object](/docs/resources/message#allowed-mentions-object) | allowed mentions for the message | false | +| components \* | array of [message component](/docs/components/reference#component-object) | the components to include with the message | false | +| files[n] \*\* | file contents | the contents of the file being sent | one of content, file, embeds, poll | +| payload_json \*\* | string | JSON encoded body of non-file params | `multipart/form-data` only | +| attachments \*\* | array of partial [attachment](/docs/resources/message#attachment-object) objects | attachment objects with filename and description | false | +| flags \*\*\* | integer | [message flags](/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (only `SUPPRESS_EMBEDS`, `SUPPRESS_NOTIFICATIONS` and `IS_COMPONENTS_V2` can be set) | false | +| thread_name | string | name of thread to create (requires the webhook channel to be a forum or media channel) | false | +| applied_tags | array of snowflakes | array of tag ids to apply to the thread (requires the webhook channel to be a forum or media channel) | false | +| poll | [poll](/docs/resources/poll#poll-create-request-object) request object | A poll! | one of content, file, embeds, poll | \* Application-owned webhooks can always send components. Non-application-owned webhooks cannot send interactive components, and the `components` field will be ignored unless they set the `with_components` query param. \*\* See [Uploading Files](/docs/reference#uploading-files) for details. +\*\*\* When the flag `IS_COMPONENTS_V2` is set, the webhook message can only contain `components`. Providing `content, `embeds`, `files[n]` or `poll` will fail with a 400 BAD REQUEST response. + :::info For the webhook embed objects, you can set every field except `type` (it will be `rich` regardless of if you try to set it), `provider`, `video`, and any `height`, `width`, or `proxy_url` values for images. ::: @@ -285,7 +287,7 @@ Returns a previously-sent webhook message from the same token. Returns a [messag Edits a previously-sent webhook message from the same token. Returns a [message](/docs/resources/message#message-object) object on success. -When the `content` field is edited, the `mentions` array in the message object will be reconstructed from scratch based on the new content. The `allowed_mentions` field of the edit request controls how this happens. If there is no explicit `allowed_mentions` in the edit request, the content will be parsed with _default_ allowances, that is, without regard to whether or not an `allowed_mentions` was present in the request that originally created the message. +When the `content` field is edited, the arrays `mentions` and `mention_roles` and the boolean `mention_everyone` in the message object will be reconstructed from scratch based on the new content. When the message flag `IS_COMPONENTS_V2` is set, the reconstructed arrays and boolean are based on the edited content in the `components` array. The `allowed_mentions` field of the edit request controls how this happens. If there is no explicit `allowed_mentions` in the edit request, the content will be parsed with _default_ allowances, that is, without regard to whether or not an `allowed_mentions` was present in the request that originally created the message. Refer to [Uploading Files](/docs/reference#uploading-files) for details on attachments and `multipart/form-data` requests. Any provided files will be **appended** to the message. To remove or replace files you will have to supply the `attachments` field which specifies the files to retain on the message after edit. @@ -307,22 +309,25 @@ All parameters to this endpoint are optional and nullable. ###### JSON/Form Params -| Field | Type | Description | -|-------------------|----------------------------------------------------------------------------------|-----------------------------------------------------------------| -| content | string | the message contents (up to 2000 characters) | -| embeds | array of up to 10 [embed](/docs/resources/message#embed-object) objects | embedded `rich` content | -| allowed_mentions | [allowed mention object](/docs/resources/message#allowed-mentions-object) | allowed mentions for the message | -| components \* | array of [message component](/docs/components/reference#component-object) | the components to include with the message | -| files[n] \*\* | file contents | the contents of the file being sent/edited | -| payload_json \*\* | string | JSON encoded body of non-file params (multipart/form-data only) | -| attachments \*\* | array of partial [attachment](/docs/resources/message#attachment-object) objects | attached files to keep and possible descriptions for new files | -| poll \*\*\* | [poll](/docs/resources/poll#poll-create-request-object) request object | A poll! | +| Field | Type | Description | +|---------------------|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| content | string | the message contents (up to 2000 characters) | +| embeds | array of up to 10 [embed](/docs/resources/message#embed-object) objects | embedded `rich` content | +| flags \* | integer | [message flags](/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (`SUPPRESS_EMBEDS` and `IS_COMPONENTS_V2` only) | +| allowed_mentions | [allowed mention object](/docs/resources/message#allowed-mentions-object) | allowed mentions for the message | +| components \*\* | array of [message component](/docs/components/reference#component-object) | the components to include with the message | +| files[n] \*\*\* | file contents | the contents of the file being sent/edited | +| payload_json \*\*\* | string | JSON encoded body of non-file params (multipart/form-data only) | +| attachments \*\*\* | array of partial [attachment](/docs/resources/message#attachment-object) objects | attached files to keep and possible descriptions for new files | +| poll \*\*\*\* | [poll](/docs/resources/poll#poll-create-request-object) request object | A poll! | -\* Application-owned webhooks can always send components. Non-application-owned webhooks cannot send interactive components, and the `components` field will be ignored unless they set the `with_components` query param. +\* The `SUPPRESS_EMBEDS` flag can be both set and unset, while the `IS_COMPONENTS_V2` flag can only be set. When the `IS_COMPONENTS_V2` flag is set, any of the used `content`, `embeds`, `files[n]` or `poll` values in the initial message must be set to `null` first, otherwise it will fail with a 400 BAD REQUEST response. -\*\* See [Uploading Files](/docs/reference#uploading-files) for details. +\*\* Application-owned webhooks can always send components. Non-application-owned webhooks cannot send interactive components, and the `components` field will be ignored unless they set the `with_components` query param. + +\*\*\* See [Uploading Files](/docs/reference#uploading-files) for details. -\*\*\* Polls can only be added when editing a deferred interaction response. +\*\*\*\* Polls can only be added when editing a deferred interaction response. ## Delete Webhook Message /webhooks/[\{webhook.id\}](/docs/resources/webhook#webhook-object)/[\{webhook.token\}](/docs/resources/webhook#webhook-object)/messages/[\{message.id\}](/docs/resources/message#message-object) From 93d7d0e3af4411ddceb557711709df4c7c56c97e Mon Sep 17 00:00:00 2001 From: b3ssel Date: Thu, 24 Apr 2025 11:45:26 +0200 Subject: [PATCH 5/7] docs: update edit message section Updated the section with the asterisk being moved from the "flags" description to the "flags" field. Removed one of the asterisks since only one was present inside the table. --- docs/resources/message.mdx | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/resources/message.mdx b/docs/resources/message.mdx index a742664d13..804a0326e5 100644 --- a/docs/resources/message.mdx +++ b/docs/resources/message.mdx @@ -908,18 +908,18 @@ All parameters to this endpoint are optional and nullable. ###### JSON/Form Params -| Field | Type | Description | -|------------------|---------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| -| content | string | Message contents (up to 2000 characters) | -| embeds | array of [embed](/docs/resources/message#embed-object) objects | Up to 10 `rich` embeds (up to 6000 characters) | -| flags | integer | Edit the [flags](/docs/resources/message#message-object-message-flags) of a message (`SUPPRESS_EMBEDS` and `IS_COMPONENTS_V2` only)\*\* | -| allowed_mentions | [allowed mention object](/docs/resources/message#allowed-mentions-object) | Allowed mentions for the message | -| components | array of [message component](/docs/components/reference#component-object) | Components to include with the message | -| files[n] | file contents | Contents of the file being sent/edited. See [Uploading Files](/docs/reference#uploading-files) | -| payload_json | string | JSON-encoded body of non-file params (multipart/form-data only). See [Uploading Files](/docs/reference#uploading-files) | -| attachments | array of [attachment](/docs/resources/message#attachment-object) objects | Attached files to keep and possible descriptions for new files. See [Uploading Files](/docs/reference#uploading-files) | - -\*\* The `SUPPRESS_EMBEDS` flag can be both set and unset, while the `IS_COMPONENTS_V2` flag can only be set. When the `IS_COMPONENTS_V2` flag is set, any of the used `content`, `embeds`, `sticker_ids`, `files[n]`, or `poll` values in the initial message must be set to `null` first, otherwise it will fail with a 400 BAD REQUEST response. +| Field | Type | Description | +|------------------|---------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| content | string | Message contents (up to 2000 characters) | +| embeds | array of [embed](/docs/resources/message#embed-object) objects | Up to 10 `rich` embeds (up to 6000 characters) | +| flags\* | integer | Edit the [flags](/docs/resources/message#message-object-message-flags) of a message (`SUPPRESS_EMBEDS` and `IS_COMPONENTS_V2` only) | +| allowed_mentions | [allowed mention object](/docs/resources/message#allowed-mentions-object) | Allowed mentions for the message | +| components | array of [message component](/docs/components/reference#component-object) | Components to include with the message | +| files[n] | file contents | Contents of the file being sent/edited. See [Uploading Files](/docs/reference#uploading-files) | +| payload_json | string | JSON-encoded body of non-file params (multipart/form-data only). See [Uploading Files](/docs/reference#uploading-files) | +| attachments | array of [attachment](/docs/resources/message#attachment-object) objects | Attached files to keep and possible descriptions for new files. See [Uploading Files](/docs/reference#uploading-files) | + +\* The `SUPPRESS_EMBEDS` flag can be both set and unset, while the `IS_COMPONENTS_V2` flag can only be set. When the `IS_COMPONENTS_V2` flag is set, any of the used `content`, `embeds`, `sticker_ids`, `files[n]` or `poll` values in the initial message must be set to `null` first, otherwise it will fail with a 400 BAD REQUEST response. ## Delete Message /channels/[\{channel.id\}](/docs/resources/channel#channel-object)/messages/[\{message.id\}](/docs/resources/message#message-object) From 7702e7f8893b093905f3a46f5c03ab8bbb8ce08d Mon Sep 17 00:00:00 2001 From: b3ssel Date: Thu, 24 Apr 2025 12:35:07 +0200 Subject: [PATCH 6/7] fix: reverted change to avoid conflicts with #7508 --- docs/resources/message.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/resources/message.mdx b/docs/resources/message.mdx index 804a0326e5..6524d6cbcb 100644 --- a/docs/resources/message.mdx +++ b/docs/resources/message.mdx @@ -625,7 +625,7 @@ For the `attachments` array in Message Create/Edit requests, only the `id` is re ### Allowed Mentions Object -The allowed mention field allows for more granular control over mentions without various hacks to the message content. This will always validate against message content or [message component](docs/components/using-message-components) content to avoid phantom pings (e.g. to ping everyone, you must still have `@everyone` in the message content or message component content), and check against user/bot permissions. +The allowed mention field allows for more granular control over mentions without various hacks to the message. This will always validate against the message and components to avoid phantom pings (e.g. to ping everyone, you must still have `@everyone` in the message), and check against user/bot permissions. ###### Allowed Mention Types From 987e3e7040d58ab84f0200543bfdf05edeb051b1 Mon Sep 17 00:00:00 2001 From: b3ssel Date: Mon, 12 May 2025 20:23:22 +0200 Subject: [PATCH 7/7] fixed table --- docs/resources/message.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/resources/message.mdx b/docs/resources/message.mdx index 6524d6cbcb..2aad13e1f8 100644 --- a/docs/resources/message.mdx +++ b/docs/resources/message.mdx @@ -806,7 +806,7 @@ When creating a message, apps must provide a value for **at least one of** `cont | files[n]?\* | file contents | Contents of the file being sent. See [Uploading Files](/docs/reference#uploading-files) | | payload_json? | string | JSON-encoded body of non-file params, only for `multipart/form-data` requests. See [Uploading Files](/docs/reference#uploading-files) | | attachments? | array of partial [attachment](/docs/resources/message#attachment-object) objects | Attachment objects with filename and description. See [Uploading Files](/docs/reference#uploading-files) | -| flags?\*\* | integer | [Message flags](/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (only `SUPPRESS_EMBEDS`, `SUPPRESS_NOTIFICATIONS` and `IS_COMPONENTS_V2` can be set) | +| flags?\*\* | integer | [Message flags](/docs/resources/message#message-object-message-flags) combined as a [bitfield](https://en.wikipedia.org/wiki/Bit_field) (only `SUPPRESS_EMBEDS`, `SUPPRESS_NOTIFICATIONS` and `IS_COMPONENTS_V2` can be set) | | enforce_nonce? | boolean | If true and nonce is present, it will be checked for uniqueness in the past few minutes. If another message was created by the same author with the same nonce, that message will be returned and no new message will be created. | | poll? | [poll](/docs/resources/poll#poll-create-request-object) request object | A poll! |