Use Dynamic Zone inside component

[wac2007]

Hello people,

I'm trying to add a Dynamic Zone inside a repeatable component but this option doesn't show inside a custom component.

Here what i'm trying to accomplish:

The options:

There's a way to "unlock" this feature or this isn't possible yet?

[derrickmehaffy]

Hello,

I see you are wanting to ask a question that is not really a bug report or a feature request, questions should be directed to the following places per the README.md:

• Stack Overflow
• Slack

For now I will mark this issue as closed, we try to keep Github clean and only for bug reports and feature requests unless there is a technical discussion that needs to happen before an RFC needs to be created. However in all 3 cases there are templates to be followed.

If you have questions or believe this was closed in error do feel free to reply.

[soupette]

@wac2007 for UI reasons we have limited the number of nested components to one. It means that you cannot create a component inside another component which is already embedded into another one.
However, the back-end and front-end code works for n levels of nested components so you can still manually create them directly in the files.

[MartinN3]

Even if you add dynamic zone inside component - it just doesn't seem to work. Not in admin nor in API.

In admin only input type text gets rendered.

And in GQL mutation is created - it cannot be mutated - it won't pass validation.

So i would say that having dynamic zone in component is not possible for now at all.

EDIT: API mutation works as expected, that means dynamic zone inside component is indeed possible. I will elaborate on my GQL mutation to validate correct implementation.

[Riya3006]

@wac2007 for UI reasons we have limited the number of nested components to one. It means that you cannot create a component inside another component which is already embedded into another one.
However, the back-end and front-end code works for n levels of nested components so you can still manually create them directly in the files.

can we add dynamic zone also inside a component through backend?

[odididi]

@MartinN3 EDIT: API mutation works as expected, that means dynamic zone inside component is indeed possible. I will elaborate on my GQL mutation to validate correct implementation.

Any hints on how you got this working?
I manually added a dynamic zone field in the model definition, however i can create anything.
Also get a This dynamic zone is not available error on the admin UI

[rlvk-vk]

@MartinN3 EDIT: API mutation works as expected, that means dynamic zone inside component is indeed possible. I will elaborate on my GQL mutation to validate correct implementation.

Any hints on how you got this working?
I manually added a dynamic zone field in the model definition, however i can create anything.
Also get a This dynamic zone is not available error on the admin UI

Yeah me too. Would be great with a solution to this, as I really need 1 level of nested dynamic zones for my current project.

[Sylvanik]

Does someone find a solution about this problem ? I see that someone solve the problem on a forked project 5 days ago.

[soupette]

Enabling the usage of a dynamic zone inside a component is not a feature we want to enable in Strapi.
@Sylvanik you can either fork the package like @benderillo did or customise your app to enable this feature.

[benderillo]

@soupette do you know if there is any plan to implement what @alexandrebodin proposed a while ago in this ticket: #5124 ?
I feel like this is more solid approach that would help many people steer clear of nesting DZ inside components. I would try and do something like this on my own fork but I am a backend dev and any frontend work is extremely painful for me because it takes ages to traverse through the source code in order to understand how things work together.

[soupette]

Which solution are you referring to in the issue?

The one that would allow creating an entry from another entry?

[benderillo]

Yes, that't the one.

alexandrebodin commented on 10 Apr 2020
@JabStrapi @Aurelsicoko I think we shoul offer support for creating relation entries directly inside the Content Manager creation view at some point so the user don't start overusing componnets instead of relations

[soupette]

For the moment, we don't plan on adding this feature to the CM we are currently actively working on other features like internationalisation and then the V4.