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
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
I'm creating a bot and I've realise that reactions field behavior is bit problematic.
Reactions field, as have been implemented, become a message object property when someone react and it's been deleted when someone unreact (undo your reaction). There's no signal that indicates a reaction have been removed. It's expected to reactions still exist (even empty or as 0), as other properties.
This turns the use of Message Object properties difficult, seems it's inconsistent.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I'm creating a bot and I've realise that reactions field behavior is bit problematic.
Reactions field, as have been implemented, become a message object property when someone react and it's been deleted when someone unreact (undo your reaction). There's no signal that indicates a reaction have been removed. It's expected to reactions still exist (even empty or as 0), as other properties.
This turns the use of Message Object properties difficult, seems it's inconsistent.
The text was updated successfully, but these errors were encountered: