Re: [community-group] Make whitespace invalid in token names (#216)

> @d34dman hm, so, with that spec, we would allow emojis?

The idea was not about allowing emojis, but to maintain the support for non latin scripts. Emoji support was a side-effect of that.

>  Or am I way off?

The proposal is different in a way that, we specify an allowed list of characters for token, instead of a dis-allow list.

JS Object's key are strings right? So then, we will need to dis-allow some characters like [".", "{", "}"], and make the list evolve into spaces and some more ¯\_(ツ)_/¯ perhaps. 

We might be better off by declaring which values are valid, instead of keeping a list of invalid characters. This way we can introduce more control characters if needed, with backward compatibility. 

E.g. A different reference format using characters like "#" and "/" as discussed here https://github.com/design-tokens/community-group/pull/259 or adding more control characters like "+" or "&" for predictable mixing and composing of tokens. At this point this is mere speculation though.




-- 
GitHub Notification of comment by d34dman
Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/216#issuecomment-2974700030 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 15 June 2025 21:26:01 UTC