We need a backend class representing the contents of the watchlist_label table:
Noting that of these four operations, only "delete label" has a referential integrity dependency on the watchlist_label_member table. WatchedItemStore could potentially manage watchlist_label_member, but asking it to also manage watchlist_label seems a step too far. It's already 1800 lines of code.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Feature | None | T3492 Enable editors to monitor edits to sets of watched pages | ||
| In Progress | None | T404391 Allow editors to organize their watchlist items | |||
| Resolved | None | T406011 Watchlist label manager | |||
| Resolved | Samwilson | T408895 Watchlist label store class |
Change #1201040 had a related patch set uploaded (by Samwilson; author: Samwilson):
[mediawiki/core@master] Add WatchlistLabelStore for watchlist label DB operations
Change #1201040 merged by jenkins-bot:
[mediawiki/core@master] Add WatchlistLabelStore for watchlist label DB operations
Change #1201863 had a related patch set uploaded (by Samwilson; author: Samwilson):
[mediawiki/core@master] Watchlist labels: Add wll_id to label object when loading all
Change #1201863 merged by jenkins-bot:
[mediawiki/core@master] Watchlist labels: Add wll_id to label object when loading all
Change #1204996 had a related patch set uploaded (by Samwilson; author: Samwilson):
[mediawiki/core@master] Watchlist labels: Add store method for deleting labels by IDs
Change #1204996 merged by jenkins-bot:
[mediawiki/core@master] Watchlist labels: Add store method for deleting labels by IDs
All done for now I think. Any remaining functionality will be picked up in the other tasks.
As this is a backend-only task, I don't think it needs to go to QA.