With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure.
Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component.
What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.
I don’t expose nested components because of this missing.
+1, the real question is really why is not already available???
Yes, this is something that was so nice from Sketch and it blows my mind Figma doesn’t support this. PLEASE Figma, add this. It’d be so simple and make a massive impact.
+1, this would be SO helpful!
+1. This is needed.
+1000 this would be a huge help and guarantee stricter enforcement of a design system!
This is a must have for design systems small or massive. Please add this as a feature.
Are we there yet?
Please add this feature.
Absolutely necessary! Right now, users of the Design System have to be very careful not to mess around with a nested property if it is also available at the main level. It is confusing and might produce undesirable results in the UI.
🙏 This is a must!!! Please add it Figma! 🙏
Not showing my hover states in the variant list would be great!
Big +1. This is necessary.
+10. We totally needed
Adding to this thread. Being able to pick which properties can be seen when using a nested instance is huge for a complex design system.
What’s interesting is you can sorta do this with the “Instance swap property” and showing “Preferred values”. This would be a similar type of idea. Showing “preferred properties” only. But in this case they couldn’t go add more properties, but even if we can just hide them that would be better than exposing all of the properties of a nested instance.
Absolutely need this.
I came here looking for this exact feature.
You can’t really build scalable, parametric design systems without this.
With the new Code connect feature, we really need this now.
Our nested symbols are often broken apart to reduce the override panel for designers but we explain to the developers to re-use the nested components those styles are suppose to follow.
With the Code connect feature, we now have nested components that are already designed but don’t display that way in the component when the developers inspect the them because of breaking them apart to cater for the over ride panel.
In order to design with the atomic approach and allow developers to know which nested component instances to use from the code libraries we need the ability to remove the other overrides for the designers but still show those built nested components to the developers.
This is a super necessary and important feature – and also very helpful for users!
I would be very happy about an implementation!
big +1 (or rather +100000)
🫶
this is a must have for nested components to work as they should
+1 pleaseeee
+1. Large components with lots of nested instances are overwhelming to designers who don’t need ALL the settings on certain components/variants.
Plus 1 for this feature.
+1 Badly need this feature for our design system.
All I want for Config!
+1 need this feature!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
