- From: Matthew Ström via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Mar 2025 00:14:34 +0000
- To: public-design-tokens-log@w3.org
I'd propose instead of standardizing on CSS idents in this case, we use the JSON spec (specifically, strings, which are the only allowed type in a key) as a foundation for token names; there are valid css idents that are _not_ valid JSON strings*, so if a dtcg file was evaluated as json then some funky things might happen. * `\a` is a valid css ident, but not a valid JSON string. -- GitHub Notification of comment by ilikescience Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/216#issuecomment-2759866673 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 March 2025 00:14:35 UTC