Skip to main content

Control nested components properties


aelveora

Please make it possible to control which properties of nested components (atoms) can be used in higher components (molecules).

What if I use same nested component in different objects and I don’t need some properties in both of them?

What if I don’t need some booleans which is part of variants of that atom in molecule?

Please fix it, thank you.

10 replies

Gayani_S
Figmate
  • Community Support
  • 1944 replies
  • December 11, 2023

2 posts were merged into an existing topic: Reorder nested porperties


Gayani_S
Figmate
  • Community Support
  • 1944 replies
  • December 11, 2023

Hey Dmitry, thank you for raising this feature request. Could you give me more information on this? I am not sure if I am understanding first request correctly.
Also, I’ve merged the third one with a similar, so you can vote on the main page.


aelveora
  • Author
  • 2 replies
  • December 24, 2023

For example.

I have Icon Button with 5 different types and 3 sizes: Small, Medium and Large. And I use this Icon Button as a nested item inside some Bar, and I want to have an option to change icons, however size and type of Button must be forbidden to change and always be Ghost and Large.

Just add checkboxes like this


Gayani_S
Figmate
  • Community Support
  • 1944 replies
  • December 29, 2023

Got it! Thank you for explaining.


Mikhail_Guguev1

When can we expect such functionality? By implementation looks like not a difficult task.


  • 1 reply
  • June 21, 2024

When will this feature be added? You can use the approach that is used in published and non-published components, if there is a dot before the name, the element will not be inherited above, if it is difficult to implement with checkboxes


Jared_Gibbons

This would be a huge improvement to maintaining consistency and mitigating the risk of designers accidentally changing defined patterns and styles in published components.


Kara_Miekina3
  • New Participant
  • 6 replies
  • September 9, 2024

PLLLEEEASSSEEEE this. please please.


Oriami
  • New Member
  • 1 reply
  • September 20, 2024


Here is a real life example where this feature is missing. In the new interface, this has become critical. I can no longer see the most important thing because the nests cover everything. Please fix this.


Raymond_Uphoff

Thought it’s A really old topic.

I think it’s the one thing Sketch is better then Figma. For years you can configure which properties are being inherited and which not in Sketch. In Figma it’s all or nothing approach. When designers apply abstraction, nested components, to keep things simple, as in not repetitive tasks, having finer control of properties is a must. Otherwise you can control the same settings on different levels and it clutters overwrite panel with, what we designers don’t like, noise!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings