(In reply to Thomas D. from comment #88)
> Comment on attachment 8557496
> Patch v2
>
> Review of attachment 8557496:
> -----------------------------------------------------------------
>
> True, but still not sufficient for ensuring absolute top ranking for *full*
> nickname matches over *partial* nickname matches, e.g.:
> Card1: Nickname="foo" (nick==searchphrase; nickIndex==0)
> Card2: Nickname="foobar" (nick!=searchphrase; nickIndex==0)
> Searchphrase: "foo"
>
> Autocomplete result (wrong):
> Card2 (partial nick match)
> Card1 (full nick match)
That result can occur e.g. when Card2 has a higher popularityIndex than Card1.
It shouldn't occur because full nickname matches (by inherent design) must supersede any other match, regardless of popularity.
(In reply to Thomas D. from comment #88) ------- ------- ------- ------- ------- ------- ------- ------- -- searchphrase; nickIndex==0) searchphrase; nickIndex==0)
> Comment on attachment 8557496
> Patch v2
>
> Review of attachment 8557496:
> -------
>
> True, but still not sufficient for ensuring absolute top ranking for *full*
> nickname matches over *partial* nickname matches, e.g.:
> Card1: Nickname="foo" (nick==
> Card2: Nickname="foobar" (nick!=
> Searchphrase: "foo"
>
> Autocomplete result (wrong):
> Card2 (partial nick match)
> Card1 (full nick match)
That result can occur e.g. when Card2 has a higher popularityIndex than Card1.
It shouldn't occur because full nickname matches (by inherent design) must supersede any other match, regardless of popularity.