Length and uniqueness constraints on labels, descriptions and aliases should be enforced by the respective change ops. They should no longer be enforced upon save.
Version: master
Severity: normal
Whiteboard: u=dev c=backend p=20 s=2014-05-06
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=62644
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T64927 Perform input validation based on ChangeOp (tracking) | |||
| Resolved | None | T64643 term validation via changeop | |||
| Resolved | None | T51583 Use standard DataValue validators for labels, descriptions and aliases | |||
| Resolved | None | T51263 Apply data type specific validators to snak values received by the API | |||
| Resolved | None | T66308 Localize error parameters for display | |||
| Resolved | None | T66309 ChangeOps should have a separate function for validation. | |||
| Resolved | None | T66311 Make ChangeOpFactory depend on entity type |
Daniel is currently working on a bunch of pretty big patch sets that also touch this issue:
https://gerrit.wikimedia.org/r/#/c/124835/
https://gerrit.wikimedia.org/r/#/c/124800/
https://gerrit.wikimedia.org/r/#/c/121422/
Change 130051 had a related patch set uploaded by Daniel Kinzler:
(bug 62643) ChangeOpFactory to depend on entity type
Change 124835 had a related patch set uploaded by Daniel Kinzler:
Move term validation into ChangeOps