Page MenuHomePhabricator

Shifting shortest "match" to beginning breaks expected display order of allowed values for a property
Open, Needs TriagePublic

Description

I am not sure if this is supported use case, but imho PF_ValueUtils::shiftShortestMatch makes no sense for local autocompletion.

We are using Property:Language, and would like to use a specific order: local languages first, rest in alphabetical order. We can almost make this happen, except PageForms shifts random shortest language name to the top.