- From: Kevin Powell via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Aug 2022 12:34:28 +0000
- To: public-design-tokens-log@w3.org
The format editors discussed this issue in this week's meeting and agreed that it's not a feature we're going to add to the specification. There are organizational and naming best practices for tokens, but the aim of the specification is to support as many different organizing principles for tokens as possible by remaining unopinionated. This proposal would force an organizational constraint that is antithetical to the goals we want to achieve with the specification. The problems raised by @TravisSpomer in https://github.com/design-tokens/community-group/issues/145#issuecomment-1172919886 surface some of the concerns we have with this approach and the solutions suggested by @c1rrus in https://github.com/design-tokens/community-group/issues/145#issuecomment-1166656970 address how to achieve similar outcomes within the existing spec. #110 is still open and may be a better place to provide further feedback on how to mark tokens as "private" in order to alter their behavior within different tools. -- GitHub Notification of comment by kevinmpowell Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/145#issuecomment-1231605308 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 30 August 2022 12:34:30 UTC