When you daisy chain symbols (nest symbol into symbol), not all the configurable options are passing through

[builderio]

When you daisy chain symbols (nest symbol into symbol), not all the configurable options are passing through

[steve8708]

hey @JefferyReidKnowde if I follow correctly, this is the expected behavior - but let me first verify I understand fully

when you create a symbol (the parent) and add a symbol within that (the child) - you can define inputs on this symbol (the parent). then when you add that symbol to a page or anywhere else, that symbols inputs should be available as user facing options. if you want the child symbol options exposed from adding the parent to pages, you'd need to make additional inputs on the parent and pass those down to the child (e.g. if you want child input named "text" to be exposed to users dropping in the parent to a page/etc - you'd need to create a "text" input for the parent, then bind that to the "text" property of the child). i.e. all options of nested symbol don't automatically bubble up to the parent (this is an interesting possible feature idea, would just have to think through any drawbacks this could possibly have, e.g. cases where maybe that's not expected and could be confusing)

anyway, if what I describe above is not what you are saying or I am misunderstanding what you are doing vs expecting please just let me know

and thanks as always for your details reports and feedback!

[steve8708]

also, I am misunderstanding - if you can link us to an example of the above that you did in Builder.io and we can see the wrong behavior in practice happy to take a look at the link, as the example may help clarify for me

[ca136]

@JefferyReidKnowde going to close this since it looks like this is currently supported. I sent an email with more details, but will be happy to re-open if we're misunderstanding what you need!