135
Allow nesting of components more than 2 levels deep
complete
k
kevinvugts
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.
Activity Feed
Sort by
Andy Xufuris
This is honestly the most annoying and frustrating thing I have ever heard of. What kind of CMS stops you from nesting components! I can't believe how long this has been complained about and the teams have done nothing about it!! So even though every other CMS software out there allows people to nest components, the message from the Strapi team is "We know better how you should be using a CMS and we can't think of any reason why you should want to nest components." Not going to add an extra level, not going to give us the option to do it, it's just too bad you are out of luck if you want to do something normal with a CMS.
Partho Ghosh
I am checking this in v4.2.2 enterprise edition, and it looks like nesting of components for more than 2 levels deep is still not possible ... attached is the component I want to embed in another component, but it never shows up in the component pick list.
Derrick Mehaffy
Partho Ghosh: I was mistaken in my update on June 15th. Within the UI we still limit it to 2 levels and for anything beyond two you need to manually edit the schema.json files.
At this time we do not plan to change the UI logic as we strongly discourage going more than 2 levels deep.
Кугичка Ластнейм
Derrick Mehaffy: Some cases really need nesting more than 2 levels deep. Is workaround exist for make possible nesting of 3 levels deep? Not 4 or more, just 3. :)
Andy Xufuris
Кугичка Ластнейм: I guess the team knows better how a customer should use a CMS. There's 120 people here that obviously disagree, but sure they know better.
Josh Corbett
Derrick Mehaffy: maybe instead of cock blocking this ability altogether, perhaps simply warn the user that's building the schema using the UI about the risks associated. It's not like this is going to harm Strapi itself, if anyone is getting harmed it's the user's own project... allow them the ability to make their own bad decisions.
Derrick Mehaffy
complete
Released in v4.2.0. The content-type builder will still limit you to 2 levels however you can add additional levels by manually editing the schema.json files.
S
Santhosh
When can we expect this in release
Derrick Mehaffy
Santhosh: It will be released with v4.2.x on June 15th
S
Santhosh
Derrick Mehaffy: Great
S
Santhosh
Derrick Mehaffy: Will this update includes the UI improvisation of this section. because if we have more 2 level UI will be congested right
Derrick Mehaffy
Santhosh: no, as mentioned in the update this is only unlocking the restrictions but the CTB and CTM will not handle them "gracefully". Our UI design is only for 2 levels so anything beyond that may or may not look right.
S
Santhosh
Derrick Mehaffy: Okay
Derrick Mehaffy
in progress
S
Santiago Santana
Derrick Mehaffy: thanks!
Derrick Mehaffy
Santiago Santana: Quite welcome :)
Derrick Mehaffy
planned
It has been confirmed internally that we will lift the hard coded restriction to return this feature to "v3 functionality" which means supporting adding them manually.
We won't add the option into the content-type builder at this time and we will consider the usage of more than 2 levels "ill-advised" due to performance and schema complexity but will allow it.
ETA / Due date are still TBD but hopefully a fix can be submitted soon
Simon Niedermayr
Please fix this!
G
Gwyn Hockridge
This basically prevents us from building anything with Dynamic components. Critical imo and preventing us from moving from v3.
Sergey Gridin
I was able to deeply nest components in v3. Hope this will get fixed soon.
L
LucaNerlich
The one feature which blocks us from creating well "organized" componet setups / reuse smaller fragments to structure our content efficiently.
Load More
→