- From: Lukas Oppermann via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Jul 2023 19:16:36 +0000
- To: public-design-tokens-log@w3.org
lukasoppermann has just created a new issue for https://github.com/design-tokens/community-group: == Specification / recommendation for custom types == Currently the specs only cover a fairly small amount of possible token types. This makes total sense considering how the specification process works. However from a user and tool developer perspective I very often run into situations where I have to move beyond what is specified. One typical case is when tokens for types that are not defined are needed. I think it would be valuable for this case to define how one should create custom types. The main issue I see is how to create a custom `$type` property name? Additionally it would be interesting when it is recommended to use composite types, vs. e.g. an array for multiple numeric values. Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/223 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 July 2023 19:16:38 UTC