- Issue created by @phenaproxima
- 🇦🇲Armenia murz Yerevan, Armenia
To make it work well, we also need to allow configuring the depth of the dependencies, and the list of reference fields to skip from exporting, because without this can produce a huge amount of unnecessary entities and even circular redirects. As an example of how to resolve this issue, we can look at this implementation: ✨ Allow to partially export content Active
- 🇺🇸United States phenaproxima Massachusetts
Good point about the circular dependencies, we should ensure we specifically test that.
I think allowing fields to opt out of being exported should be admin configurable and happen in a follow-up, as it might have some additional complexity best handled separately.
As for dependency depth control — why? What would the use case be for such a thing?
- 🇦🇲Armenia murz Yerevan, Armenia
About the depth - let's imagine a "page" node which has a reference field "related_articles" with several articles, and each article has a field "related_pages" linked to some pages - by exporting this, we can get a pretty long nested structure, and even loops.