You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the initial implementation of #310 (in #627), we'll order the suggested topics purely by recency (see #627 (comment)). That matches zulip-mobile's behavior, and is enough to be quite useful.
In Zulip web, though, there's some further ranking: an exact match comes first, then prefix matches, then matches that start at a word boundary. (Plus prefix matches are further split by case-exact vs. case-insensitive.) See initialize_topic_edit_typeahead in web/src/composebox_typeahead.ts; and then follow the indirections to triage_raw in web/shared/src/typeahead.ts for the implementation.
I'm not sure all the nuances of that are good to copy — in particular the case behavior, which should perhaps just be all case-insensitive. But we should do either that or something like it.
The additional ordering should, like in web, be stable — results that have the same priority in this ranking should remain ordered by recency.
This is a post-launch issue because the zulip-mobile legacy app doesn't do this ranking.
The text was updated successfully, but these errors were encountered:
In the initial implementation of #310 (in #627), we'll order the suggested topics purely by recency (see #627 (comment)). That matches zulip-mobile's behavior, and is enough to be quite useful.
In Zulip web, though, there's some further ranking: an exact match comes first, then prefix matches, then matches that start at a word boundary. (Plus prefix matches are further split by case-exact vs. case-insensitive.) See
initialize_topic_edit_typeahead
inweb/src/composebox_typeahead.ts
; and then follow the indirections totriage_raw
inweb/shared/src/typeahead.ts
for the implementation.I'm not sure all the nuances of that are good to copy — in particular the case behavior, which should perhaps just be all case-insensitive. But we should do either that or something like it.
The additional ordering should, like in web, be stable — results that have the same priority in this ranking should remain ordered by recency.
This is a post-launch issue because the zulip-mobile legacy app doesn't do this ranking.
The text was updated successfully, but these errors were encountered: