add message.call field #6864
add message.call field #6864
Conversation
|
Thank you for the PR! We have this field marked explicitly as private internally, and not part of the public API. If you ever want to check - we explicitly call out which fields we support in our Open API spec: |
|
After further deliberation we've decided to mark these fields as public. the initial reasoning behind why they were private was because apps could not actually ever see this field in the course of normal operations (you couldn't call apps, and apps could not participate in GDMs) where this field would be present. But now with user apps, and it being available in interactions, apps can indeed see this field as part of their normal operations. As such we're accepting this PR, and as well updating the OpenAPI specs to expose these fields as public. |
docs/resources/Channel.md
Outdated
|
|
||
| | Field | Type | Description | | ||
| | participants | array of snowflakes | array of [user](#DOCS_RESOURCES_USER/user-object) object ids that participated in the call | | ||
| | ended_timestamp | ?ISO8601 timestamp | time when call ended | |
There was a problem hiding this comment.
this is not guaranteed to be populated if/when the call ends. it's best effort.
|
spec says call is nullable - when is that the case and should that be reflected in the docs? |
https://github.com/discord/discord-api-spec?tab=readme-ov-file#known-issues |
4 participants
available to bots in interactions so why not