Nested Components (more than 2 levels from the UI)
complete
k
kevinvugts
We want to update the interface to be able to nest more than 2 levels of components in the administration panel. This feature is supported if you update your Content-Types schemas manually. We want to ease everyone's life by supporting this natively from the UI.
--
Original post:
Currently while building websites with Strapi as a back-end it annoys us as developers that we cannot use more than 2 levels deep of nesting components in the newer versions of Strapi. Take for example a Hero component including a set of cards, and a set of cards also includes buttons which link to different sections in your website. This is simply not possible with newer versions in Strapi.
Aurélien Georget
FYI, we will remove the limits of 2 components. It should be available very soon. Even if we know the user interface might not scale properly, it will unlock some of you while allowing us to capture more precise feedback regarding the use cases and what's need to be updated in the UX/UI.
Marco Autiero
Merged in a post:
Allow nesting of components more than 2 levels deep in UI
Daniel Byta
I've recently read all the materials regarding the ban on creating deeply nested components. I saw that many people are asking to promote this feature within 3 years. I also saw that you removed the restriction for creating such structures in a raw schema.
It seems to me that this is an incomplete solution to the community's request.
In this regard, I have a proposal to add the ability to create such structures in the UI so that Strapi matches its stated capabilities to create any data structures easily, out of the box and without extra effort.
Considering the fact that such structures may not be very efficient in terms of using dbms resources, I propose making the functionality disabled by default, but with the ability to enable it in the settings.
Honestly, I don’t see any real objective system restrictions in order to allow editing such structures in the UI. From the outside it looks like 1 PR with a slight change in the layout of the entities module and 1 PR with remove restriction on the server side.
Because I saw the Strapi rep's response regarding this proposal. The answer was something like this: “This feature is not in our plans yet” and we do not believe that it is advisable to include it in our plans entirely. I'd like to see a more expanded answer on this.
Why do you think this functionality is not needed?
What technical difficulties led you to this decision?
Why did you unlock this functionality when editing the json schema, but did not unlock it in the UI?
Why is there a depth limit of 2?
Finally, I personally think this feature is critical. Because the existing limitation forces us to reinvent the wheel.
So, what is your official advice to prevent creating deep nested components need?
V
Viktor Kim
Derrick Mehaffy
I see that this feature marked as completed
But how it works?
I'm trying to make a menu using nested components
The structure is pretty simple (screen 1)
when i'm adding content, and save - everything looks ok, but if i will try to publish, i'm getting an runtime error.
For testing i've used the latest strapi v5.20.0, node v20.17.0
Douwe Pausma
I still can't seem to be able to nest a dynamic zone in a dynamic zone, I would like to create a columns component, in which you can select various other components like Text or an Image component. Using Strapi 5
Caleb
Even in Strapi 5 I cant seem to nest dynamic zones only repeatable components.
Derrick Mehaffy
marked this post as
complete
Added in Strapi 5
Alex Provozen
Derrick Mehaffy How can I test it?
Nilay Khandhar
Derrick Mehaffy: how can we test this?
Nilay Khandhar
This feature is in progress since 21st May as per chat history.
Can anyone confirm the timeline when it will launch?
Also will this feature comes only for cloud or for self hosted as well?
Caleb
Any update on the timeline of this?
Aurélien Georget
marked this post as
in progress
Aurélien Georget
FYI, we will remove the limits of 2 components. It should be available very soon. Even if we know the user interface might not scale properly, it will unlock some of you while allowing us to capture more precise feedback regarding the use cases and what's need to be updated in the UX/UI.
Faruk Kutlu
If Strapi engineers had designed a train with cabinets for long distance travelling, it would definitely have no seats as third level components. Because they know better than people that if you sit while travelling in nested cabinets in wagons, you may not be able to get off the train safely in an emergency.
Thanks God Almighty that Strapi engineers are just developing CMSs.
Load More
→