"Weird" search live completion result order?

[hartwork]

When switching to Spanish+English and typing "gato" (for animal cat in Spanish), I see this:

What's surprising here is that:

• Sort seems case sensitive without intention (but that's a guess)
• Longer words appear before shorter words, while sharing identical prefix.

Is that known and intended?

[karlb]

This is not intended. The scoring used here is max_score * rel_importance but rel_importance is null, thereby throwing off the whole sorting algorithm. It works much better when is use max_score * coalesce(rel_importance, 0.01), but I want to check whether rel_importance is allowed to be null at all and remind myself of the exact meaning of these variables before pushing a fix.

I assume https://github.com/karlb/wikdict-web/issues/9 has the same underlying reason.

[hartwork]

This is not intended.

Okay, nice.

[..] and remind myself of the exact meaning of these variables before pushing a fix.

Looking forward to that.

I assume #9 has the same underlying reason.

I have a feeling that there is a hardcoded limit saying "words of length 3 are too short" as well. True?
Though maybe that's off-topic here 🤷

[karlb]

I have a feeling that there is a hardcoded limit saying "words of length 3 are too short" as well. True?

Three letters should be sufficient, but words shorter than that won't get completed. After three letters, a completion list for words starting with these letters is fetched and used as the user continues typing. This reduces latency while typing and is more cacheable than doing a request after each letter.

[hartwork]

With 3bd80b5 applied I get this:

Cool! 🎉 Any chance you could re-deploy production from master?

[karlb]

Cool! tada Any chance you could re-deploy production from master?

Done, see also today's blog post.

[hartwork]

@karlb https://www.wikdict.com/en-es/ is still putting "gato" after "Gato Risón", even after forced reload. Am I missing something?

[hartwork]

Chromium seems fine, but it's still broken in Firefox. Turns out that the https://www.wikdict.com/typeahead/en-es/gat response is cached, will only expire ~30 minutes from now, and forced reload is being ignored on that resource. Oh my 😃 So I guess it will work fine from 16:00 UTC+1 then…

[hartwork]

So I guess it will work fine from 16:00 UTC+1 then…

Works in Firefox now as expected 👍