Expose/hide nested instances -> at component property level

389 replies
21392 views

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.

Show previous replies

Apolline

Active Member

@Lindsey_Drennan Oh but 5 months ago we got this message don’t worry :)

Hey all, PM responsible for Component Props. Just wanted to say totally hear the desires and needs for this feature, and it’s something we intend to build at some point. Right now other DS-related features are ahead in priority for us, but part of those priorities do include updates to component props. This is not a forgotten part of the product - were still doing active development here.

The priority is not one of the most active thread on the forum, that should be a basic feature, no, don’t worry. It’s probably another shiny thing they can brag about on social media and during keynotes so they can say they have more features than other products.

Apolline

Active Member

Danae Nestorides

New Member

Just adding on to continue the traction

+1 from my DS team, it would be super useful to have this

rbccwbr

New Member

+1

Christian5

New Member

Essential feature in my opinion, please follow up, figma Team 🙏🏻.

Aayla

New Member

Huge +1 on this. As the design system owner, I need to be able to allow designers to change certain properties in a nested component while preventing them from changing other properties as easily.

I have many situations where this is needed, but one example is: allowing people to change the value of a text property, without having access to all of the other properties of the nested component (like the size, color, etc.)

BerndBauer

New Member

This would be awsome

Alfirastel

New Member

+1 for this:

I have many situations where this is needed, but one example is: allowing people to change the value of a text property, without having access to all of the other properties of the nested component (like the size, color, etc.)