Currently, in order to check if a variable value is set correctly, you need to apply it to a text or field. It would be great to have a way to debug/inspect a variable in runtime, especially for those that are not displayed on screen.
9 Likes
I have a similar issue as well.
What I expect to see here is: Under themeStyle = Light, Primary text = gray-700 (Unfortunately, such description is not visible in the current Inspect / Colors).
1 Like
Some way to inspect variables or see the current state of all the variables would be real handy now that you can do conditional logic in prototyping.
2 Likes
Agree. For example at the moment I am working on a prototype where clicking radio buttons should set a variable, but it doesn’t seem to be working. I’m sure I’m doing something wrong but being able to check a variable value while clicking through the prototype would be really helpful to debug where I’ve gone wrong.
1 Like
modes in variables table are just for… some basic use cases, it is not a replacement for Tokens System, so let the extra fields remain, less bugs is alwais a good target
2 Likes
This is absolutely a must-have feature after Figma added advanced variable logic. I am beside myself bashing my head against the wall trying to figure out whether an issue I’m facing has to do with a mistake I made or with buggy variable implementation by Figma; there’s pretty much no way for me to figure it out without some formal debugger feature. Furthermore, if it is a Figma bug, it would make it so much easier for me to file a bug report. Please add this!
1 Like
I’m sure the debugger as we se it wont come out soon, guys at Figma might already thinking about it but as a One-for-All super-mega game changing solutions with blows and whistles.
So for now the trick is making a debugger by hand from some text blocks and assigning the variables you are playing with in your prototype. And som boolean components too, like a test panel with lights. Sounds time consuming, but you will save on debugging sessions later