Inaccurate design tokens group name conflict message

[LauraKalbag]

@xanderjakeq from the screenshot it looks like the conflicting name is test.border?

Is it possible that you might not have another token called test.border but have a token called something like test.border.solid/test.border.[someOtherName]?

These would be treated as a conflict as a group name cannot be the same as a token name. Natacha explains why here:

CAnnot add design token alias

Hey, this is not a bug. I’ll try to explain it: Design token names are built from token paths. Periods (.) are used to nest tokens groups. Then, the last segment of the token name corresponds to the token. The thing is that a token name cannot also be a token group. So in the example you are using: bs.color.blue creates this nested structure: bs /* group */ color /* group */ blue /* token */ But bs.color.blue.500 creates this one: bs /* group */ color …