For channel.suspicious_user.message, fragment.type == "text" never occurs, despite that being a documented possibility.
Thus, the fragments array does not behave like fragments for every other chat eventsub topic and the corresponding pubsub topic (low-trust-users), so it is not possible to reconstruct the full message with the fragments array (as is usually possible).
The fragments array should include each text component, not just emotes/cheermotes (just like the pubsub equivalent, and other chat eventsub topics)
Additional context or questions
This bug fix can occur in v1 or v2. If a v2 topic is created, please fix the casing for the Cheermote field name (should be a lowercase C)... also it'd be nice if message_id was moved out of the message object for consistency with other chat eventsub topics
Brief description
For
channel.suspicious_user.message
,fragment.type == "text"
never occurs, despite that being a documented possibility.Thus, the
fragments
array does not behave likefragments
for every other chat eventsub topic and the corresponding pubsub topic (low-trust-users
), so it is not possible to reconstruct the full message with thefragments
array (as is usually possible).EventSub example:
PubSub example:
How to reproduce
channel.suspicious_user.message
Expected behavior
The
fragments
array should include each text component, not just emotes/cheermotes (just like the pubsub equivalent, and other chat eventsub topics)Additional context or questions
This bug fix can occur in v1 or v2. If a v2 topic is created, please fix the casing for the
Cheermote
field name (should be a lowercase C)... also it'd be nice ifmessage_id
was moved out of themessage
object for consistency with other chat eventsub topics