- From: Travis Spomer via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Apr 2022 00:18:02 +0000
- To: public-design-tokens-log@w3.org
Sorry, I don't follow how that really applies here. This spec isn't about defining tokens in CSS. If someone, like the people in that video, wants to invent their own method of specifying tokens in some CSS-like syntax, they're welcome to. But that would be a different format, not the one in this spec (albeit perhaps one meant to interoperate with this one 1:1)! And the author of that format could solve that problem however they wish.
This issue is saying "hey, parsing strings to get numbers is dumb; we should just separate the data in the format itself instead of parsing a string." `"50"` is a number and `"px"` is a string for a unit. But there's no situation where there's any confusion or ambiguity between parsing a token name and a value.
If in the future there were some syntax where `red.6a50` was a valid value, there still wouldn't be any ambiguity, because references to token names are in braces as in `{red.6a50}`.
--
GitHub Notification of comment by TravisSpomer
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/121#issuecomment-1085259382 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 April 2022 00:18:03 UTC