Page MenuHomePhabricator

[Task] Implement "Value only constraint"
Closed, ResolvedPublic

Description

Someone defined a "Value only" constraint in the templates, probably meaning properties wioth this constraint aren't allowed to be used as qualifiers or reference.

Event Timeline

Jonaskeutel raised the priority of this task from to Low.
Jonaskeutel updated the task description. (Show Details)
Jonaskeutel added a subscriber: Jonaskeutel.
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Lydia_Pintscher renamed this task from Implement "Value only constraint" to [Task] Implement "Value only constraint".Aug 17 2015, 4:12 PM

Some properties should only be used either as a value or as a source, but we don't have a constraint for that yet. Maybe instead of having special value only/qualifier only/source only constraints, there should just be one constraint that specifies which of the three should or shouldn't be allowed.

Change 381005 had a related patch set uploaded (by Lucas Werkmeister (WMDE); owner: Lucas Werkmeister (WMDE)):
[mediawiki/extensions/WikibaseQualityConstraints@master] Add “used as value only” constraint type

https://gerrit.wikimedia.org/r/381005

Change 381005 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Add “used as value only” constraint type

https://gerrit.wikimedia.org/r/381005

Change 382712 had a related patch set uploaded (by Lucas Werkmeister (WMDE); owner: Lucas Werkmeister (WMDE)):
[mediawiki/extensions/WikibaseQualityConstraints@master] Update method names in ValueOnlyCheckerTest

https://gerrit.wikimedia.org/r/382712

Change 382712 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Update method names in ValueOnlyCheckerTest

https://gerrit.wikimedia.org/r/382712