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 Jun 17, 2024. It is now read-only.
It's an odd behavior that the on should be holding the subtype instead of the type.
In my case I'm trying to make a bot read the currently added emojis, instead of .on('emoji_changed') or even .on('emoji_changed.add') I'm forced to use .on('add') which is not clear enough.
Is there any chance that the bot can also receive a type.subtype pair? That would be really descriptive and clear.
I'm also worried that the add subtype is part of another event, say file.add and it will give false positives.
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.
It's an odd behavior that the on should be holding the subtype instead of the type.
In my case I'm trying to make a bot read the currently added emojis, instead of
.on('emoji_changed')
or even.on('emoji_changed.add')
I'm forced to use.on('add')
which is not clear enough.Is there any chance that the bot can also receive a
type.subtype
pair? That would be really descriptive and clear.I'm also worried that the
add
subtype is part of another event, say file.add and it will give false positives.The text was updated successfully, but these errors were encountered: