I’ve created a nested component and was hoping the properties of the nested component are carried through to the parent component. But this seems not the case. Also creating the properties again on the parent and assign them to the nested instance is not possible. This limits the usecase of nested components quite significant.
Thank you for the report. I have moved this to the “Improvements” category and have shared this internally with the team to discuss what would be the best way to provide control over nested component properties when editing a parent component instance.
@charaf Could you please provide an update on this topic?
We are heading in to multiple, large site builds which will utilize several dozen components in Bricks. How we handle component structure hinges on whether this item is addressed or not. Thank you
The properties should not automatically be exposed to the parent component. However, even in Bricks 2.0 RC you can’t pass a property value to a sub-component.
We have added this to our list of planned improvements. We will evaluate whether it is better to automatically “bubble up” the properties of nested components, or to provide a way for passing parent component property values as parameters to nested components.
I don’t even think that’s necessary, just let us assign parent properties to the sub component property fields. I was legitimately surprised that I wasn’t able to.
Without being able to link parent properties to a child component the nested components feature is kinda “useless”. Was just going to update our sites with the release of 2.0 - merged the global elements and everything else that made sense into componentens, wanted to create the first “card” component with a child component and was “shocked” i couldnt assign a parent property to the child so i had to create the “main” component 3x now to cover the different cases
it would help a lot if the component properties are defined as a dynamic tag, in case you want to use them in Code blocks or have a text that is partially dynamic
No to “bubble up”… yes to “scoped components”. Scoping will also future-proof further dev.
Example… I have 4 components on the page (say a dashboard), with a button on the page that I want to ‘trigger’ something in a specific component. If any of these components, or even worse, nested components, share same IDs / classes… this will be a mess to handle… and even worse if one has to revisit months later.
Scoping would make every instance, even nested instances… ‘unique’.
I recently discovered Bricks after two years of building websites with Elementor, and I’m genuinely impressed! Personally, it just needs that one essential feature before I can start using it daily for my clients’ websites. I’ll be following this topic closely, and I’m ready to purchase Bricks as soon as this feature is released!
> It should be possible to create components where any internal element that could be nested is exposed as nested (“[x] Act as a slot” toggle). So that way, you can create component instances that external elements can populate.
).