Re: [community-group] Composite Token Composition (#179)

@CITguy the editors have reviewed this proposal. It's an interesting idea that could DRY up some token source files, but the level of complexity for vendors to implement is higher than we want to add to the spec at this time.

Alias usage within a composite token will allow "parts" of a composite token to be reused across multiple composite tokens. It will require being more verbose than what you're proposing, but right now we believe the tradeoff in favor of clarity over brevity is where the spec needs to go.

```
"base-font-family": {
  "$value": ["Arial", "sans-serif"],
  "$type": "fontFamily"
},
"base-font-weight": {
    "$value": 400,
    "$type": "fontWeight"
},
"type-heading-1": {
  "fontFamily": "{base-font-family}",
  "fontSize": "48px",
  "fontWeight": "{base-font-weight}",
  "letterSpacing": "0px",
  "lineHeight": 1.25
},
"type-heading-2": {
  "fontFamily": "{base-font-family}",
  "fontSize": "36px",
  "fontWeight": "{base-font-weight}",
  "letterSpacing": "0px",
  "lineHeight": 1.1
}
```

-- 
GitHub Notification of comment by kevinmpowell
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/179#issuecomment-1400436724 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 23 January 2023 14:26:26 UTC