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
I'm always frustrated when group messages appear under the "message" event, which I primarily use for direct or private conversations. It becomes confusing and requires extra filtering logic to distinguish between group chats and individual chats.
I would like the platform to introduce a new event, such as "message.group", dedicated exclusively to group messages. This way, the existing "message" event can remain focused on private or direct messages, simplifying the handling of different conversation types.
I considered manually filtering incoming messages to detect whether they come from a group or an individual. However, this approach adds complexity to the code and can lead to potential errors or overlooked cases.
Implementing a dedicated "message.group" event would help developers better organize their workflows and reduce the need for custom logic to differentiate between group and private messages.
The text was updated successfully, but these errors were encountered:
I'm always frustrated when group messages appear under the "message" event, which I primarily use for direct or private conversations. It becomes confusing and requires extra filtering logic to distinguish between group chats and individual chats.
I would like the platform to introduce a new event, such as "message.group", dedicated exclusively to group messages. This way, the existing "message" event can remain focused on private or direct messages, simplifying the handling of different conversation types.
I considered manually filtering incoming messages to detect whether they come from a group or an individual. However, this approach adds complexity to the code and can lead to potential errors or overlooked cases.
Implementing a dedicated "message.group" event would help developers better organize their workflows and reduce the need for custom logic to differentiate between group and private messages.
The text was updated successfully, but these errors were encountered: