We want to allow EntityContent to represent redirects; the knowledge about how redirects are encoded in the JSON structure should not be in Entity (since Entity doesn't know about redirects), not should it be in EntityContent or EntityHandler (since these are not available on the client).
Therefore the serialization code needs to be factored into a standalone service object.
Version: unspecified
Severity: normal
Whiteboard: u=dev c=backend p=3 s=2014-06-03
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T68067 Support Redirects between Items (tracking) | |||
| Resolved | Lucie | T59745 Automatically create redirects when merging items | |||
| Resolved | None | T59744 Implement Redirects in ItemContent | |||
| Resolved | None | T68024 Factor entity content serialization out of EntityContent (and friends) | |||
| Resolved | None | T70730 Factor interaction logic out of MergeItems API module, for re-use in SpecialMergeItems | |||
| Declined | Lydia_Pintscher | T91415 Optionally create redirect after clean merge via MergeItems API module or special page. |
Change 134373 had a related patch set uploaded by Daniel Kinzler:
Introducing EntityContentDataCodec