- From: James Nash via GitHub <sysbot+gh@w3.org>
- Date: Sun, 26 Jun 2022 22:56:55 +0000
- To: public-design-tokens-log@w3.org
In the current spec, tokens can either have actual values - which, to use your terminology, would make them an "option" or "primitive" token - or they can be references to other tokens - often called "alias" tokens. I believe the 2 kinds are already easy to distinguish for both tools and humans. The rule is: If the token's `$value` is a string in the form `"{path.to.other.token}"`, then it's an alias token. Otherwise, it's an "option" token and the `$value` is the actual token value. Furthermore, the `"{path.to.other.token}"` value of an alias token clearly identifies which other token it's pointing to. I'm therefore struggling to understand what additional info a `$reference` property would contain and how that would make the relationship between alias token and option token clearer than it already is. @reblim could you perhaps provide an example of how you'd expect `$reference` to be used? Maybe that'll help me better understand your intent. -- GitHub Notification of comment by c1rrus Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/141#issuecomment-1166669883 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 26 June 2022 22:56:57 UTC