Callback response of type DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE ignores IS_COMPONENTS_V2
Closed this issue · 3 comments
Description
Currently, it is not possible to set the IS_COMPONENTS_V2 flag on a deferred reply. This means you have to set it on the subsequent edit request, if you intend to use components v2.
Steps to Reproduce
Reply to an interaction with this callback response:
{
"data" : {
"flags" : 32768
},
"type" : 5
}The resulting message has flags 128 (LOADING) but not IS_COMPONENTS_V2. According to the docs the IS_COMPONENTS_V2 flag can be set:
Message flags combined as a bitfield (only SUPPRESS_EMBEDS, EPHEMERAL, IS_COMPONENTS_V2, IS_VOICE_MESSAGE, and SUPPRESS_NOTIFICATIONS can be set)
Expected Behavior
The resulting message should have the IS_COMPONENTS_V2 flag set when it was set in the request body.
Current Behavior
The IS_COMPONENTS_V2 flag is ignored.
Screenshots/Videos
No response
Client and System Information
API v10
My mistake, this seems to be intended behavior according to the footnote
I still think this bad API design, to silently just drop flags instead of giving an error when the flag is unsupported.
