You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our elevation shadows stack the different core shadows and we'd like to not have to duplicate those definitions. We would like to use useRefValue, so the token relationships would be visible in Figma Tokens as well. This is impossible currently due to how our tokens are defined and the FT issue I linked above.
Is there an easy way of adding some sort of filtering to useRefValue, so that the specific shadow.elevation.small.value would not use references, but everything else still would?
The text was updated successfully, but these errors were encountered:
I see, yeah I guess we can make a little something to work around that problem, I propose a boolean metadata flag that you can put in your token (as a sibling to the value prop) to flag it was "ignore this one for useRefValue function".
Ooh that seems nice! This is definitely a better workaround than not using references at all, but it does lose the internal color reference currently. If this is more difficult to solve, I understand, does not matter too much.
I'm trying to work around this Figma Tokens issue: tokens-studio/figma-plugin#706
Our shadow tokens are defined as follows:
Our elevation shadows stack the different core shadows and we'd like to not have to duplicate those definitions. We would like to use
useRefValue
, so the token relationships would be visible in Figma Tokens as well. This is impossible currently due to how our tokens are defined and the FT issue I linked above.Is there an easy way of adding some sort of filtering to
useRefValue
, so that the specificshadow.elevation.small.value
would not use references, but everything else still would?The text was updated successfully, but these errors were encountered: