Skip to main content
Question

Valid Naming for Wrapper Components

  • April 1, 2025
  • 1 reply
  • 7 views

Damon_Tolhurst

Question:

Is there any clever way to name component variants that doesn’t create properties?

 

Context Details:

My company is using a third-party UI kit for a design system.  In order to create customizations, I’m looking to have a separate Figma file that imports the UI kit, but only including the parts we want designers to use.  Then we’ll publish our version of the design system to be used.  In order to get only our subset of components to be available in design files, I need to wrap the UI kit components in a new component.  Since the original components already have the properties set up, it doesn’t make sense to duplicate them on the wrapper component.  But if I don’t use the ‘property=value’ format for the wrapper component variables, Figma yells at me.  Maybe that’s just something to live with?  But I’m curious if anyone else has run into this and found a solution.

1 reply

Damon_Tolhurst

So far, the best I’ve come up with is just having a dummy property like “variant=1” that then gets ignored when using the component.  It just sits at the top while the nested (i.e. real) properties are listed below.


Reply


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