Skip to main content

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.

+1

 

It’s incredible that after 2 years and 300 replies of users asking for that, we still have to read that this is not a priority right now… But anyway, as a DS maintainer for a huge company with many Figma users, this would be absolutely helpful, and I’m giving here my vote too.

 

 

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.

 


+1 please! Desperately need this for our design system 😭


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.

I know you have other priorities but can you give us a clue as to how far back in your backlog this is? ​@jjcm 


+1

I wish we will get it soon, that’s necessary to build strong modular DS.


Yes, this would be very helpful for creating composed components.


I’d like this to see the light of day asap! It’s been over 2 years and this small, but important, feature request is still not in the hands of Figma users? With 13 pages of requests? And yes, I know it certainly might be bigger than it first seems but over 2 years is not acceptable for a feature like this.


+1

Absolutley needed, this is especially painful not to have as a library designer


Off topic: Don’t you also wish changing Breakpoint for Card would also change Breakpoint for Button as well? ​@Zoltan_Szalay 


+1

 

I came expectant
I saw 2 years of requests 
I got sad … and left


+1 This would be huge!


+1 high priority


+1


+1 Things are getting really crazy. 


+1 This is absolutely ridiculous for a tool that's supposedly design system centric. Sketch has had a robust manage overrides interface for years.

 


+1

Come on guys. Seriously.


Can’t believe that 2 years later this still isn’t a thing..

+1


+1 


+1


Sketch has had this for years—controlling which things can be Overrides. 


+1


+1


+1


+1 Very long due features.


Shouting into the void again - 
Cannot customize overrides at nested instance level, and cannot re-order component props(including exposing nested props) in a manner that would allow for a hacky manual work around.


 


+1