- From: Travis Spomer via GitHub <sysbot+gh@w3.org>
- Date: Sat, 02 Jul 2022 15:57:17 +0000
- To: public-design-tokens-log@w3.org
I was actually in a meeting just this week that was caused by our "option" (global) tokens not being exported to code in one case—we needed to surface those in some fashion for third-party extensibility. And I was in a chat a couple of weeks ago about our shadow tokens, which don't fit nearly into either bucket and are treated like "option" tokens but are technically alias tokens since their colors point to other tokens that change with the theme. Each project using tokens is going to have different technical and design requirements. I think this sort of thing is best left to project-specific rules. Baking it into the format in any way adds unnecessary constraints that would be very burdensome for anyone who had different needs. -- GitHub Notification of comment by TravisSpomer Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/145#issuecomment-1172919886 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 2 July 2022 15:57:19 UTC