Allow Developers to View Full List of Variables in a File

+1 Any news?
Our developers still can’t access primitives/tokens. They need to use plugins(which often don’t work as expected) > JSON > parser… If something changes in the variables, they have to repeat the whole process. Has anything changed? Or only proper / automated way is syncing DS with Github (Enterprise seat)?

Figma: Let’s make variables!
Designers: Yaaay!
Figma: But let’s make developers suffer.
Developers in dev-mode: You can’t see tokens in dev mode that you paid for

+1
Using Variables everywhere seems great for designers, but why hide them from devs even in Dev Mode?

+1, this is a big pain in the butt, since I have to additionally spec color tokens > primitive colors > HEX values in my mockups, instead of Figma doing all these mundane chores automatically for me. Please prioritize this, folks 🙏

+1. Need the ability to use variables within Dev Mode for effective collaboration.

+1. This feature is needed to have all parties on the same tag system for multi platform UI

Has this been implemented?

+10 for this feature - even something as simple as exporting the variables into an excel or google sheet as a quick fix would mitigate some of the major issues here. Currently managing a variable library of over 1200 tokens, the ability to manage versions or keep track changes before they are Github ready (where our eng. design tokens live) is painful. My eyes have crossed so many times trying to figure out how to streamline this effort.

@Mohit_Tater’s plug-in is the best thing I’ve found that will allow you to view everything in a list format. Thank you for your effort here! But still need some native functionality to rectify this issue ☹

My current use case involves managing core color variables and token variables within our design system. Designers frequently use core color variables when assigning colors, while token variables are primarily for maintaining color consistency across components and aren’t used directly by designers.

To streamline the color selection process and avoid clutter from unused token variables, I decided to unscope these token variables so they wouldn’t appear in the color options. This solution effectively removed unnecessary colors from the selection menu.

However, this change introduced a new issue: if we need to use a token variable for a specific component, we now have to manually scope the variable, publish the library, apply the color, and then unscope the variable and publish the library again. This process is cumbersome and not ideal for efficient workflow management.

All of this to say, a simple checkbox for “view all scopes” or “ignore scoping” in the color options menu when picking a color would solve this problem.

Hey @Tyler_Aikey, thanks for the feedback!

We’ll pass this onto the team for future consideration.

It is a must have to work efficiently with developers 🙄