How to turn off the global?

[AndySobol]

Hi!
I have a problem, it used to work properly. Updated package configuration to 4 versions and in vain. These files are automtaically assigned to the global group that prevents me from working. There is no time to convert json files. So that’s how to turn off this automatic function of inserting the global group?

UPD: Solved the issue of setting in config file) Excuse me

[jorenbroekema]

When this repo was made, tokens studio (formerly figma tokens plugin) was creating something called "tokensets", not entirely sure if they still use this but basically the topmost "key" of the tokens object would be the tokenset name, so for example take these two files in style-dictionary tokens:

core-colors.json:

{
  "core": {
    "color": {
      "grey": {
        "50": {
          "value": "#000000",
          "type": "color",
        },
        "100": {
          "value": "#222222",
          "type": "color",
        }
      }
    }
  }
}

semantic-colors.json:

{
  "color": {
    "primary": {
      "base": {
        "type": "color",
        "value": "{core.color.grey.50}"
      }
    }
  }
}

These two would be converted to:

figma-tokens.json:

{
  "global": {
    "core": {
      "color": {
        "grey": {
          "50": {
            "value": "#000000",
            "type": "color",
          },
          "100": {
            "value": "#222222",
            "type": "color",
          }
        }
      }
    },
    "color": {
      "primary": {
        "base": {
          "type": "color",
          "value": "{core.color.grey.50}"
        }
      }
    }
  }
}

So both the color primary semantic tokens and the core color palette will get combined into 1 object, with a "global" parent key, which is the name of the "tokenset" in the plugin. I have to insert this "global" key by default, otherwise by default your conversion would not result in a working JSON for the figma plugin, because it would think that there are two "tokensets": color and core, and the reference core.color.grey.50 would then no longer work.

You can however customize the tokenset names, explained in the readme under Features, first one in the list.

Hopefully this makes sense :)