Page MenuHomePhabricator

Sort warning-types in menu by their description, not their internal name
Open, LowPublic

Description

Example config excerpt from en.wikipedia.org:

warning-types:

warning: Vandalism
spam: Spam
attack: Personal attacks
test: Editing tests
delete: Removal of content
blank: Blanking pages
npov: Biased content (not adhering to NPOV)
genre: NPOV genre change
fringe: NPOV fringe
error: Factual errors
bio: Inappropriate biographical content
speedy: Removal of speedy deletion template
afd: Removal of an AFD template
unsor: Failing to cite a verifiable reliable source
nor: Original research
chat: Using talk page as forum
mos: Manual of style

Sorting this list alphabetically by the first column, which is the current behavior, creates a weirdly sorted list in the user interface. I have always wondered about that sorting before I saw the configuration file and finally understood where it comes from.

Please sort this list by the second column.

Event Timeline

Closing as intentional and not really required, per https://github.com/huggle/huggle3-qt-lx/issues/278 -- Thank you very much for the tip. :)

Oh no. Reopening. This is a maintenance nightmare.

Please make the sorting column configurable, at least.

https://github.com/huggle/huggle3-qt-lx/issues/278#issuecomment-380642117

Here's another problem: Renaming the default "warning" seems to break the default vandalism revert key "Q". How should Huggle know that "02100_warning" is the default?

Are all the problems that come with this decision really "intentional"?

Petrb triaged this task as Low priority.May 13 2018, 7:47 PM
Petrb subscribed.

That shouldn't break anything if you use default-template: "warning" per https://www.mediawiki.org/wiki/Manual:Huggle/Deploying/DefaultConfig.yaml

That shouldn't break anything if you use default-template: "warning" per https://www.mediawiki.org/wiki/Manual:Huggle/Deploying/DefaultConfig.yaml

Oh! That line was completely missing from the en.wikipedia configuration; I should have had a look at the global default too!

Thank you very much for the tip, that actually solved the problem. :)

(Note: This bug isn't affecting the reporter anymore, but might still be nice to have)