- Issue created by @balintbrews
- 🇺🇸United States tedbow Ithaca, NY, USA
I think to find the number of pages or content entities in general that use a specific component we might need 📌 Ensure querying JSON nested values when parent keys are unknown is possible in all supported databases Needs work or more likely 📌 Calculate field and component dependencies on save and store them in an easy to retrieve format Active
Also one thing to note, 📌 Calculate field and component dependencies on save and store them in an easy to retrieve format Active won't directly get us the number of instances as it would just say if it was used at least 1x on a content entity.
from the summary
Display information about pages that currently use the code component.
Is it good enough to show how many pages use the component but not how many instances of the component there actually are?
So if a component is used on 2 pages but on 1 page it is placed 3x should the number shown be 1 or 4(1 page 1x + 1 page 3x)?
Also we want show indirected uses, correct? Meaning if Component A is used on 1 page by placing the Component A directly on the page and another page by placing Component B that imports Component A, that would show 2 uses, correct?
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
AFAICT 📌 Calculate field and component dependencies on save and store them in an easy to retrieve format Active would actually provide the necessary information! 🤞🤓
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
📌 Calculate field and component dependencies on save and store them in an easy to retrieve format Active is in!
This is now technically possible!
@lauriii: how important is this? Is it in scope for 🌱 Milestone 1.0.0-beta1: Start creating non-throwaway sites Active ?
- 🇫🇮Finland lauriii Finland
This is not a beta or stable blocker but would be a nice improvement to build. Moving to active in case someone from the community wants to pick this up ✌️