10000 CV2: Add missing limits for alt texts, ID clarifications by freya022 · Pull Request #7537 · discord/discord-api-docs · GitHub
[go: up one dir, main page]
Skip to content

CV2: Add missing limits for alt texts, ID clarifications #7537

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

CV2: Add missing limits for alt texts, ID clarifications #7537

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ef70de8
Add limits to alt texts
freya022 May 2, 2025
8da4441
Clarify pre-CV2 component IDs, 0 ->1 behavior
freya022 May 2, 2025
05abf7d
Move pre-CV2 notes to "Legacy Message Component Behavior"
freya022 May 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/components/reference.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -924,7 +924,7 @@ To use this component, you need to send the [message flag](/docs/resources/messa
| type | integer | `11` for thumbnail component |
| id? | integer | Optional identifier for component |
| media | [unfurled media item](/docs/components/reference#unfurled-media-item-structure) | A url or attachment |
| description? | string | Alt text for the media |
| description? | string | Alt text for the media, max 1024 characters |
| spoiler? | boolean | Whether the thumbnail should be a spoiler (or blurred out). Defaults to `false` |

###### Example
Expand Down Expand Up @@ -954,7 +954,7 @@ To use this component, you need to send the [message flag](/docs/resources/messa
| Field | Type | Description |
|--------------|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------|
| media | [unfurled media item](/docs/components/reference#unfurled-media-item-structure) | A url or attachment |
| description? | string | Alt text for the media |
| description? | string | Alt text for the media, max 1024 characters |
| spoiler? | boolean | Whether the media should be a spoiler (or blurred out). Defaults to `false` |

###### Example
Expand Down Expand Up @@ -1172,6 +1172,8 @@ To upload a file with your message, you'll need to send your payload as `multipa

Before the introduction of the `IS_COMPONENTS_V2` flag ([see changelog](/docs/change-log/2025-04-22-components-v2)), message components were sent in conjunction with message content. This means that you could send a message using a subset of the available components without setting the `IS_COMPONENTS_V2` flag, and the components would be included in the message content along with `content` and `embeds`.

Messages preceding components V2 will contain an `id` of `0`, sending back `0` is allowed but will be incremented to 1, then generated sequentially while avoiding duplicates.
Copy link
Contributor

Choose a reason for hiding this comment

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

How about "Legacy message component's id will start at 0 with each following id incrementing by 1"


Apps using this Legacy Message Component behavior will continue to work as expected, but it is recommended to use the new `IS_COMPONENTS_V2` flag for new apps or features as they offer more options for layout and customization.

:::info
Expand Down
0