You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sending a button component (components v1) with a string emoji (i.e.: emoji: "<:BlahajReach:1213502811870986321>") fails with data.components[0].components[0].emoji[MODEL_TYPE_CONVERT]: Expected an object/dictionary. This is due to Discord.JS no longer resolving "<:BlahajReach:1213502811870986321>" (emoji mardown) to an object for the Discord API, even though the Typescript types allow passing a string, and prior versions of DiscordJS supported that case. This seems to be a regression in discord.js@14.19.0.
Either please remove the string type definition, or properly resolve emoji strings again. This is very annoying, especially in a large code base.
Which package is this bug report for?
discord.js
Issue description
reference: https://discord.com/channels/222078108977594368/824411059443204127/1369347560128512096
Sending a button component (components v1) with a string
emoji
(i.e.:emoji: "<:BlahajReach:1213502811870986321>"
) fails withdata.components[0].components[0].emoji[MODEL_TYPE_CONVERT]: Expected an object/dictionary
. This is due to Discord.JS no longer resolving"<:BlahajReach:1213502811870986321>"
(emoji mardown) to an object for the Discord API, even though the Typescript types allow passing astring
, and prior versions of DiscordJS supported that case. This seems to be a regression indiscord.js@14.19.0
.Either please remove the
string
type definition, or properly resolve emoji strings again. This is very annoying, especially in a large code base.Code sample
Versions
Issue priority
Medium (should be fixed soon)
Which partials do you have configured?
GuildMember, Message, Reaction
Which gateway intents are you subscribing to?
AutoModerationConfiguration, Guilds, GuildExpressions, GuildInvites, GuildMembers, GuildMessageReactions, GuildMessages, GuildVoiceStates, GuildWebhooks, MessageContent
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered: