Skip to main content
Roxanne_G_UX
July 6, 2023

LAUNCHED: Include color variable alias in dev mode side panel

  • July 6, 2023
  • 50 replies
  • 5460 views

Hi. I have set up all my color variables in my design system “App_Usage_Collection.” But my devs use storybook and they call the colors by their primitive names, so I set up another collection of color variables called _Storybook. I alias the Storybook Primitives in the App_Color_Usage collection. BUT in dev mode I only see the app_color_usage collection variable name, not the alias. Can we also please see the alias listed? Thanks! 🙏

50 replies

Joshua_Kenzie
February 22, 2024

My dev team are complaining that they can only access Hex values, this is useless information now that we’re trying to use semantic colour names

Alice_Holm
Active Member
February 23, 2024

I also really need this so our devs can see the alias, please Figma!

Blackwood
New Member
March 15, 2024

Sometimes it feels like Figma holds off on most requested features for the annual Config conference just so that they have stuff to announce.

I’d far rather they just ship continuously.

That said, the latest multi-edit feature is fantastic.

Mahana_Delacour
March 22, 2024

the same goes for other types of variables like Spacing

Mahana_Delacour
March 22, 2024

the same goes for other types of variables like Spacing ! Please have this for dev mode

Paloma_Pedrosa
New Member
April 8, 2024

We need this otherwise there is not easy way to share variables with devs. I have a lot of them already!!

stefan_koch
April 19, 2024

Need this urgently! Using plugins like variables2css to bridge that issue can only be a temporary solution.

Joao_Rios1
July 11, 2024

Still needing this a LOT for alias tokens in our DS… It doesn’t make sense to use an alias token for color if devs will only see the HEX value.

Nathan_Phillis
July 25, 2024

Extremely frustrating as a dev trying to implement color tokens.

  1. You can’t see what a token inherits from.
  2. Given #1 you logically go to look for the list of tokens to figure out what it is.
  3. You can’t even see the definitions of all the tokens.

How the hell are you supposed to figure out what something like button/fill-primary is then?
Given how hard it is to figure out what tokens, even getting a consistent way of using them across the team is a disaster, with people using hexcodes directly, some using half-complete token implementations that don’t inherit from each other + the list goes on on with how many ways I’ve seen this root cause fragment implementations.
This is literally an unusable feature without plugins in it’s current state that does more harm on the dev side then good on the design end.

Lucas_Campos
August 21, 2024

I really need this feature! In the meantime, my team is using this approach (which I personally think is a workaround, but it works).

I created primitive tokens and allocated them into styles, so the inspection panel returns this structure to me.

The perfect scenario would be if the panel returned this same structure for aliases, so I wouldn’t have to work with styles.