Yes, totally agree. I feel like this shouldn’t be a choice.
Running into this issue trying to assign a boolean variable to a boolean property in a nested component. In order to achieve this, I need to break the component link which breaks the whole point of having things built in a component.
I would agree with this as well; something I just ran into myself. I started looking into nested components and updating the properties in the nested components, but that doesn’t seem to be a win as a workaround for this topic since those can only be updated via the instance selected, and you can’t attach variables to those properties created either (which I think could be a good supplement to the variables feature). Would love for this to get fixed since nesting components is widely used, especially for any dropdown, navbar, or menu!
2 Likes
Also running into the nested component issue with variables.
It feels like one of the major hurdles that needs resolving to fully adopt a variable workflow.
I would say this is more important than any other variables issue right now. Anyone building a design system will have used nested components and will have hit this issue after building out all their design system components, only to find they can’t set variables to nested components, frequently used in Dropdowns, Overlays/Popovers, Lists, Menus etc
very much looking forward to getting support for this.
edit - workaround right now is to just not make a collection of Components into a Component, but just keep them in a frame and copy and paste it. Feels a bit wrong and updating it would mean replacing all of the instances of that duplicated Frame if you need to make changes. Workaround is basically more manual work 
I might be talking nonsense - or this might already be possible 
, but hear me out.
What if we could set a variable to a component property? 
I was working with a dropdown and thought this could be useful since I have a main component for the dropdown and I want to use it in multiple instances with different text and different placeholders.
Just a thought 
In need of this feature asap, without the ability of setting variables to nested instances I still get cluttered screens because of having to duplicating everything unnecessarily and the workflow is really awful that way. Same with an option to switch variable modes through prototype to make it interactive without workarounds.
-
- As a user I want to be able to assign variable values to nested components so that I can significantly reduce the number of instances of a complex component.
Yup, I really need this as well. Seems counter-intuitive that I’d have to detach an instance to assign variables to the nested instances…