2.0: Fix variable references when references aren't coming from any active themes

Closes https://github.com/tokens-studio/figma-plugin/issues/2906

When we're creating variables, we currently use themes that are active to inform what variables should be used as references. However, if those theme groups aren't active, we won't know what variable references to use for tokens and will fall back to raw hex values inside variables. Especially in multi-file setup users sometimes only enable one theme group, meaning they won't have the necessary references available.

What does this pull request do?

Changes the logic to add another set of themes to the merge function, so that the references from the current theme group have preference, but after that we'll take into account other themes.

Note that this is kind of flawed as we will pick the first available variable reference that we find. However, I'd say it's OK enough, given:

We should educate users that they should keep tokens only to one theme group
Eventually we should refactor themes so that users can directly specify what theme group a variable reference should be coming from

Before:

After:

Testing this change

Create multiple theme groups
One theme group should reference token from another
Create a multi-file setup (you need to push to git to do that)
Create and Publish variables from the first theme group in file A
Go to file B, activate the library from file A via Figma
Create variables from the second theme group (that's using tokens from the first one) in file B

With this change, the references correctly map. Before, they used hex values.

tokens-studio / figma-plugin

2.0: Fix variable references when references aren't coming from any active themes #2911

What does this pull request do?

Testing this change

⚠️ No Changeset found