- From: Jerome Farnum via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Sep 2022 10:50:04 +0000
- To: public-design-tokens-log@w3.org
> Stronlgy typing the spec could be a great solution to many of the current issues. I really like this from @KyleWpppd `the definition could be either a token has a $value or an $alias. The syntax for alias tokens might then disallow a $type field because the type is from the aliased token.` what are the arguments against this? I don’t think it’s a fair assumption that all token references will be singular direct aliases to another token. I’ve seen dimensional tokens that combine two other dimensional tokens (sum, product, etc), color tokens that may mix an opaque RGB color token with a token for an alpha value. Providing a token that effectively maps to a CSS shadow requires at least two dimension values and color. -- GitHub Notification of comment by jeromefarnum Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/141#issuecomment-1252176793 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 September 2022 10:50:06 UTC