[Wikidata-bugs] [Maniphest] [Commented On] T172134: Proposal: Create "number of values" constraint type and replace "single value"/"multi value"

Esc3300 added a comment. In T172134#3488911, @Lucas_Werkmeister_WMDE wrote: @Esc3300 I’m not sure what you mean –isn’t that “item requires claim” / “value requires claim”? This has currently a constraint for P 106=politician, but maybe we should have a 2nd value in P 106 for items with that

[Wikidata-bugs] [Maniphest] [Commented On] T172134: Proposal: Create "number of values" constraint type and replace "single value"/"multi value"

Nikki added a comment. I would prefer to keep the existing single value constraint because it's a very common constraint and replacing it wouldn't have any benefits for users (or would it?). Being able to specify how many values a multi-value constraint should have sounds perfectly reasonable,

[Wikidata-bugs] [Maniphest] [Commented On] T172134: Proposal: Create "number of values" constraint type and replace "single value"/"multi value"

Lucas_Werkmeister_WMDE added a comment. @Esc3300 I’m not sure what you mean –isn’t that “item requires claim” / “value requires claim”?TASK DETAILhttps://phabricator.wikimedia.org/T172134EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:

[Wikidata-bugs] [Maniphest] [Commented On] T172134: Proposal: Create "number of values" constraint type and replace "single value"/"multi value"

Lucas_Werkmeister_WMDE added a comment. Note: even if we do remove the “single value” and “multi value” constraint types, we should keep the messages and use them if the allowed range is [1, 1] or [2, ∞), which will probably still be the most common cases.TASK