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
API: Deprecate FormatEmojiAPI in favor of a simpler function #42
Comments
You're only supposed to use |
But it's used by |
Well, yes, but APIEmoji is just a type alias to string; it's only meant to add extra connotation on the differences of syntax for custom emojis between contexts (messages, in code, in API). |
K, I'll replace it with a comment |
FormatEmojiAPI
takes two parameters, the first one being optional, which is not very idiomatic.Also
FormatEmojiAPI
doesn't even return aEmojiAPI
type, but astring
.Also, if we're doing this
APIEmoji
might be a better name, since this is an emoji used by the API and not an API for emojis.Therefore, I propose to either deprecate or delete
FormatEmojiAPI
in favor of two new functions:Additionally,
APIEmoji
should get aURLEncode() string
method, that URL encodes the emoji for safe API usage.Can hand in a PR for this
The text was updated successfully, but these errors were encountered: