example: selecting "kelly" is a needless chore, because you have to sift through a bunch of kelly emojis to find the one named kelly. similar things happen with "slammer" and several others.
the canonical name of an emoji should always have precedence over keywords in the picker
limitations of the emoji picker library, unfortunately. can only give it a list of strings to search through.
would adding "kelly" to the tags of :kelly: do it you think? it would double match then
I also am seeing in the code that we seem to put the keywords first in the array of strings for a given emote:
return [...customEmoji!.keywords.map(y => y.keyword), customEmoji!.custom_emoji.shortcode].join(',');Maybe re-ordering that to put shortcode first would help? I haven't used that library so idk
Or maybe the library just does "once there's an exact match shrug your arms and sort it alphabetically". shit
yeah iirc, it just tries to match it the best it can and sort alphabetically.
I know this is a convenience thing not a discoverability thing but the emoji mart (click on the little smiley above the comment/post text box) has better search
but also yeah, this is annoying and an unforeseen consequence of keywords
This is ultra annoying if you look for "laugh", since they show up in alphabetical order you get all the "agony" emoji first, which makes no sense.
