mirror of https://github.com/zulip/zulip.git
afba77300a
So far, when ordering typeahead suggestions, any query matches that did not occur at the start of the target string were considered equally. So for example, for the query "ok", "squared_ok" and "smoking" were allotted equal priority, which does not make sense. Now, matches from a word boundary (space, hyphen, underscore or slash) are given priority (after exact matches and beginning matches), so that in the above example, "squared_ok" is regarded as a better match than "smoking". Since recipients' sorting is complex, and needs word boundary matches separately for decoupled sorting post triage, `triage_raw` is extracted from `triage` to return the raw matches. Fixes: #24127. |
||
|---|---|---|
| .. | ||
| fenced_code.ts | ||
| internal_url.js.flow | ||
| internal_url.ts | ||
| poll_data.js.flow | ||
| poll_data.ts | ||
| resolved_topic.js.flow | ||
| resolved_topic.ts | ||
| typeahead.js.flow | ||
| typeahead.ts | ||
| typing_status.js.flow | ||
| typing_status.ts | ||