MergeItems is the most complex API module we have and it needs quite some refactoring/splitting up. What and how exactly should be discussed and turn into small actionable items.
Version: unspecified
Severity: normal
Whiteboard: u=dev c=backend p=5 s=2014-08-26
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T68067 Support Redirects between Items (tracking) | |||
| Resolved | Lucie | T59745 Automatically create redirects when merging items | |||
| Resolved | None | T71106 Rewrite SpecialMergeItems based on ItemMergeInteractor | |||
| Resolved | None | T70730 Factor interaction logic out of MergeItems API module, for re-use in SpecialMergeItems |
(updated the summary, changing scope slightly)
MergeItems is not that complex compared to EditEntity or even GetEntities. However, before we add more functionality (like automatically creating redirects), we want to factor the interaction logic (aka business logic) out of the API module, so it can be reused by the correspinding special page.
Relevant patch https://gerrit.wikimedia.org/r/#/c/151145/
Should be sufficient, I made a new ticket for refactoring SpecialMergeItem (bug 69106).