-
-
Notifications
You must be signed in to change notification settings - Fork 739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistency between Emoji and Emote #816
Comments
Does Discord even make a distinction between Emoji and Emotes in the API? Edit: outside of Discord, Emoji and Emotes are used interchangeably, so if the distinction is not concrete in the API, I would argue we shouldn't make it concrete, either. |
With #793, since we're going to be importing a list of emojis from Unicode, we may as well expose Parse/TryParse on Emoji to accept an alias, while still retaining the constructor for pre-encoded emoji strings. As for keeping a concrete distinction, Discord does provide an Emote structure in the API (at the guild-level). Removing Emoji would put us back at the original behavior, where |
Emote: To give expression to emotion. Mostly they can be used interchangeably in this case. But 🆎 is definitly not an emote. ;) |
@BinkanSalaryman did you read the issue? The definition has nothing to do with the issue. The point of the issue was to point out the inconsistent implementation. Edit: Also, the terms used in this lib all follow the terms defined by Discord. Emote is specifically for a custom guild emote, while Emoji is for standard Unicode ones. |
@Still34 I did, why so pricky? I hope I lifted your confusion that drove you to submit the naming as an issue!
Discord only defines emoji, desktop application has written emoji too in server/guild settings. Where did emote come from? |
Apologies if I sounded hostile; Edit: I re-read the comment and apologies that I thought you were replying to the issue itself rather than making a suggestion to the changes, my bad. |
At the time of writing, to create an
Emoji
object, you'd have to pass the unicode into its public constructor; to create anEmote
object, you'd have to do it through either theParse
or theTryParse
method, and the object's constructor isinternal
only.This feels extremely inconsistent and can sometimes be confusing.
The text was updated successfully, but these errors were encountered: