- From: Travis Spomer via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Oct 2022 05:23:11 +0000
- To: public-design-tokens-log@w3.org
I think that the biggest concern there would be this: 1. you start using a non-standard `textAlignment` type with values `left`, `right`, and `center` 2. a year from now a `textAlignment` type is added to the spec with values `start`, `end`, and `middle` 3. now your tooling barfs on standard token files that use the word `start` because your tooling expected `left` That's a bit contrived though. And if you named your non-standard `textAlignment` property `custom.textAlignment` or the like, that problem goes away entirely. --- On the topic of this issue: for what it's worth, I was definitely against the JSON primitive types being allowed as valid token types before reading James's post today, but I have successfully been converted to the pro-primitive-types side with that `$extensions` example. If we assume that most tools will simply ignore tokens with those types, they suddenly become very useful. -- GitHub Notification of comment by TravisSpomer Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/120#issuecomment-1279665313 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 October 2022 05:23:12 UTC