hexbear

10261 readers

2 users here now

Now that the old Hexbear fork has been officially abandoned, this community will be used as a space for meta-discussion on the site itself.

founded 4 years ago

MODERATORS

[email protected]

the emoji picker has a bug: keywords take precedence over the actual name of the emoji (hexbear.net)

submitted 2 months ago by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 9 points 2 months ago (1 children)

limitations of the emoji picker library, unfortunately. can only give it a list of strings to search through.

[–] [email protected] 7 points 2 months ago* (last edited 2 months ago) (1 children)

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

[–] [email protected] 6 points 2 months ago

yeah iirc, it just tries to match it the best it can and sort alphabetically.