@jamie You mean “to the parent instance”, right? See WIP: Bricks 2.0 Alpha: Nested component properties not shown on instance - #6 by charaf.
@aslotta I mean if I have “Component B” inside “Component A”, how do I pass field values from the instance of “Component A” to “Component B”?
Edit: I see from that link, this is not yet possible. I agree with:
What makes sense is a one-click solution to expose a sub-component property as property of the current component.
just wait for the slots to be developed
locking a component inside another component doesnt makes sense as well thats weird.
nestable/inner/slots are way to go
when slots comes you will be able to combine any slotable component with any other component so that solves every nesting needs.
rightnow we dont have a choice we have to wait for it to be developed. hopefully it comes this year…
1 Like
Do you mean what we have currently? I.e. you can add a component inside another, but its values are locked in to the parent component? It’s better than nothing, but not very flexible.
My use case is a component (lets call it “A”) comprised of an image and a content box component (lets call it “B”) which has a title, some text and a button. That way, I can reuse component “B” outside of component “A”.
thats slots
slots will solve all nesting needs
go vote for it if you didnt yet it is almost 100
it is already WIP I dont know why we are voting tho 
it is clear that it has to be developed lol…
1 Like