- Issue created by @phenaproxima
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
With 📌 [PP-1] Consider not storing the ComponentTreeStructure data type as a JSON blob Postponed , that would become a lot simpler to achieve.
This spun off from
✨
Content templates, part 3b: store exposed slot subtrees on individual entities
Active
. In that issue, we're changing ComponentTreeItem to store multiple subtrees as individual field items, each tied to a specific slot that is exposed by the full view mode's content template. If the template changes such that a slot no longer exists, or is no longer exposed, entities' ComponentTreeItem values will have stale data.
Whenever a ComponentTreeItem is saved, it should be automatically purged of any items that are targeted at slots in the template which are no longer exposed.
None.
Active
0.0
Data model
With 📌 [PP-1] Consider not storing the ComponentTreeStructure data type as a JSON blob Postponed , that would become a lot simpler to achieve.