Currently, EntityContent is much too long and has too many responsibilities. Some refactoring is needed to move most of the code out of this class into separate helper classes which then can also be easily exchanged and reused for other entity types.
The ultimate goal would be to get rid of EntityContent or only use it for ids and maybe redirect things.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T109579 [Epic] Give more sister projects access to Wikidata | |||
| Open | None | T187900 There is no way to reference a specific quote on Wikiquote | |||
| Stalled | None | T71753 [Story] Wikibase / Wikidata support on Wikiquote | |||
| Invalid | None | T71752 Refactor EntityContent (tracking) | |||
| Resolved | None | T67531 Remove getTitle() from EntityContent | |||
| Open | None | T69238 Factor diff logic out of EntityContent | |||
| Resolved | None | T64493 Remove save(), getPage() and related methods from EntityContent | |||
| Resolved | None | T64210 deprecate EntityContent::save() (fix lots of tests) | |||
| Resolved | daniel | T63264 Implement EntityStore service | |||
| Resolved | None | T64211 EditEntity should use EntityStore | |||
| Resolved | None | T64491 Repo API modules should not depend on EntityContent |
Yes and no. Refactoring EntityContent is an ongoing task that will never end. We don't need this ticket to do this, especially since this tickets description is quite vague and not really actionable.