- From: Travis Spomer via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Oct 2022 18:28:16 +0000
- To: public-design-tokens-log@w3.org
Hi Lukas—is it possible you missed the section about the [`$extensions` node](https://design-tokens.github.io/community-group/format/#extensions)? That's where we're planning on adding all of the properties that we need that aren't covered by the spec, including for cases like that specific one.
In a case like your example, my current thinking is that we would probably do something like this:
```json
{
"textHighlightError": {
"$value": "#ff000080",
"$type": "color",
"$extensions": {
"proprietarystuff.calculatedtoken": {
"base": "{color.base.red}",
"opacity": 0.5
}
}
}
}
```
Then spec-compliant tools would at least still know that it's red at 50% opacity, but tools that understand `proprietarystuff.calculatedtoken` know how to recalculate the color if anything changes.
--
GitHub Notification of comment by TravisSpomer
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/174#issuecomment-1276571751 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 October 2022 18:28:18 UTC