bug: Sharkey should report exact match for emoji query first
Created by: kio
💡 Summary
When using the admin/emoji endpoints (could apply to other endpoints as well) - the exact match is not returned as the first result. this is problematic for programs looking for a needle inside a large haystack of >100, as you'd have to programatically have to dig to the bottom.
🥰 Expected Behavior
-> admin/emoji/list-remote
query: "miku", host: "shonk", limit: 1
<-
[
{
id: 'falseid',
aliases: [],
name: 'miku',
category: null,
host: 'shonk',
url: 'shonk.picture/shonk',
license: null,
isSensitive: false,
localOnly: false,
roleIdsThatCanBeUsedThisEmojiAsReaction: []
}
]
🤬 Actual Behavior
-> admin/emoji/list-remote
query: "miku", host: "shonk", limit: 100
None of the emojis are an exact match to the query!
📝 Steps to Reproduce
No response
💻 Frontend Environment
* Model and OS of the device(s):
* Browser:
* Server URL:
* Misskey:
🛰 Backend Environment (for server admin)
* Installation Method or Hosting Service:
* Misskey:
* Node:
* PostgreSQL:
* Redis:
* OS and Architecture:
Do you want to address this bug yourself?
-
Yes, I will patch the bug myself and send a pull request