It's been proposed that we should support tokens that also have sub-tokens. Today, if you have Global.Color.Red and also specify Global.Color.Red.100, the latter is ignored. We could likely support and remove some of the assumptions in the existing code. It does, however, add complexity when aliasing. We would probably then declare that any token that has sub-tokens is itself not a set. Using { "aliasOf": "Global.Color.Red" } would always refer to the single Global.Color.Red token, and not any of the tokens beneath it.
There is not currently any scenario that requires this, but the plugin developers seem to want it; they may know of a scenario.
It's been proposed that we should support tokens that also have sub-tokens. Today, if you have
Global.Color.Red
and also specifyGlobal.Color.Red.100
, the latter is ignored. We could likely support and remove some of the assumptions in the existing code. It does, however, add complexity when aliasing. We would probably then declare that any token that has sub-tokens is itself not a set. Using{ "aliasOf": "Global.Color.Red" }
would always refer to the singleGlobal.Color.Red
token, and not any of the tokens beneath it.There is not currently any scenario that requires this, but the plugin developers seem to want it; they may know of a scenario.