Skip to content

Conversation

@DV8FromTheWorld
Copy link
Member

@DV8FromTheWorld DV8FromTheWorld commented Sep 22, 2025

Addresses #7787

@DV8FromTheWorld DV8FromTheWorld requested a review from a team as a code owner September 22, 2025 14:57
@DV8FromTheWorld DV8FromTheWorld requested review from abe-discord and removed request for a team September 22, 2025 14:57
@anthonydiscord anthonydiscord requested review from anthonydiscord and removed request for abe-discord September 22, 2025 15:35
@anthonydiscord anthonydiscord merged commit 39a92dc into main Sep 22, 2025
4 checks passed
@anthonydiscord anthonydiscord deleted the bug/update-components-v2-edit-explanation branch September 22, 2025 15:35
| 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.
\* 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`, or `poll` fields must have their values reset to empty. For `content` and `poll` this is `null`. For `embeds` and `sticker_ids` this is `[]`. Failing to do this will result in a 400 BAD REQUEST response.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of them should be able to be set to null, we shouldn't have to set a list.
Or is L933 wrong..?

All parameters to this endpoint are optional and nullable.

onerandomusername pushed a commit to onerandomusername/discord-api-docs that referenced this pull request Sep 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants