-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
Message forwarding #6833
Message forwarding #6833
Conversation
@shaydewael this is ready to be merged. |
docs/resources/Channel.md
Outdated
| message\* | [message] | subset of fields in the [message object](#DOCS_RESOURCES_CHANNEL/message-object) | | ||
|
||
\* The current list of message fields subset consists of: | ||
'type`, `content`, `embeds`, `attachments`, `timestamp`, `edited_timestamp`, `flags`, `mentions`, `mention_roles`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'type`, `content`, `embeds`, `attachments`, `timestamp`, `edited_timestamp`, `flags`, `mentions`, `mention_roles`. | |
`type`, `content`, `embeds`, `attachments`, `timestamp`, `edited_timestamp`, `flags`, `mentions`, `mention_roles`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it intended that mention_roles
is only returned on the Get Message(s) endpoints?
Add documentation for message forwards. A message forward gives users the ability to send a snapshot of a message in one channel to another channel. - snapshots are immutable, and do not receive updates from the original message (unlike replies) - similar to a REPLY message, a forward is created using a `message_reference` # Examples ## Responses ```json { "author": { "id": 123456789012345678, }, "message_reference": { "type": 1, // FORWARD "message_id": 123456789012345678, "channel_id": 123456789012345678, "guild_id": 123456789012345678 }, "message_snapshot": { "content": "hello world", "embeds": [ // Embed objects ], "attachments": [ // Attachment objects ], } } ```
|
||
#### July 15, 2024 | ||
|
||
We are slowly rolling out the message forwarding feature to users. This feature allows callers to create a message using `message_reference.type = FORWARD` and have the API generate a `message_snapshot` for the sent message. The feature has [some limitations](#DOCS_RESOURCES_CHANNEL/message-reference-types) and the snapshot is a minimal version of a standard `MessageObject`, but does capture the core parts of a message. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are slowly rolling out the message forwarding feature to users. This feature allows callers to create a message using `message_reference.type = FORWARD` and have the API generate a `message_snapshot` for the sent message. The feature has [some limitations](#DOCS_RESOURCES_CHANNEL/message-reference-types) and the snapshot is a minimal version of a standard `MessageObject`, but does capture the core parts of a message. | |
We are slowly rolling out the message forwarding feature to users. This feature allows to create a message using `message_reference.type = FORWARD` and have the API generate a `message_snapshot` for the sent message. The feature has [some limitations](#DOCS_RESOURCES_CHANNEL/message-reference-types) and the snapshot is a minimal version of a standard message object that only captures the core parts. |
Co-authored-by: val.le <81811276+valdotle@users.noreply.github.com>
Co-authored-by: val.le <81811276+valdotle@users.noreply.github.com>
Co-authored-by: val.le <81811276+valdotle@users.noreply.github.com>
Co-authored-by: val.le <81811276+valdotle@users.noreply.github.com>
Reopens #6818 since it's not released yet
https://app.asana.com/0/1206892657968723/1207348897116878