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.
Another practical benefit/use case for this in design system work:
Being able to hide/disallow the editing of certain properties in specific contexts would help our Figma components to be more self-documenting for our engineers
Scenario:
We recently had a dev on our team run ahead building the React Native counterparts to a handful of new Figma components. And the recent strides Figma has made in building bridges between design and implementation has made this more frictionless than ever, with our dev able to self-serve basically everything they needed directly through Dev Mode.
However, one of the components in question included a few nested instances. And, because certain of these nested properties needed to be configurable by consumers of the parent component (e.g., text strings and icon swaps), those nested instances’ properties are exposed.
So our dev’s implementation wound up including all of the nested properties, including several that absolutely should not change in the context of this specific parent component (as changing them can break the layouts and screw up their visual representation of state).
And the React Native component itself wound up being both more complex (with numerous unnecessary parameters) and more potentially brittle (liable to breakage) than necessary.
Right now, resolving this disconnect requires an extra layer of verbal or textual instruction on which properties to include and which to ignore for each component.
If we were instead able to explicitly hide those properties from design system consumers, the component property configuration itself (whether viewed through the Dev Mode playground or accessed through some manner of code integration) could itself potentially serve as a standalone contract between Design and Engineering, without any extra layer/side-channel of accompanying documentation being necessary.
If I could heart this a thousand times, I would!!!
again me 🙋♀️
We need this function. At the moment, we are building individual components in a more complex way so as not to expose all the properties of the nested components. The whole workflow would be solved by simply turning the properties on and off. Please add this, it would help many designers when building components.
A definite must, in my case I have set styles that I don’t want the user to change (they’re determined by the parent), and wish to expose other props like the text override.
After almost 2 years, still waiting for this…
Should we discard the idea that this will happen someday? or… can we think that it will come at some point? @Celine_Figma
Honestly, If you can prioritize this kind of initiatives to others like mouse pointer customization… it would REALLY help to library building teams worldwide.
it will almost have been 2 years since this idea was posted, so i am posting to both upvote this and celebrate its birthday 🥳
happy birthday post
🤣
+1 for this, i need to clean up the mess we have in DS files so bad
I made some Figma Slides if that helps to convince to prioritize the feature request.
Figma – 12 Sep 24The tl;dr: Just expose all nested components with a toggle to turn on nested properties with fine-grained control.
+1 We also need this functionality in our designsystem.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
