- From: Lukas Oppermann via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Oct 2022 09:00:16 +0000
- To: public-design-tokens-log@w3.org
lukasoppermann has just created a new issue for https://github.com/design-tokens/community-group: == Clarification needed for custom properties in tokens == In the specs document some [additional properties](https://design-tokens.github.io/community-group/format/#additional-properties) are mentioned. However it is not state if custom properties are allowed or not. From our perspective it would be very beneficial if custom properties would be allowed. For example we have a lot of case were we reference a base color `{color.base.red}` but need to add transparency to it. For this we use a custom `alpha` property. The resulting token looks like this: ```js { "textHighlightError": { "$value": "{color.base.red}", "$type": "color", "alpha": 0.5 } } ``` I know that alpha and other transformations are mentioned in issue #137 and others. But even if this gets added to the specs I feel there may always be needs for custom cases. Having a clear way to implement those would be very helpful. Either by allowing properties without `$` or by defining an additional prefix for custom properties. Or simply by stating that tools may ignore any non-standard properties but per spec they may be added. Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/174 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 09:00:18 UTC