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

Sorry for pinging an old PR; was just reviewing the open ones. If we want to ban whitespace, should we do something like say adopt CSS’ identifier syntax? Where `foo bar` isn’t allowed, but `foo\ bar` is (escaping).

Of course, this would get weird in JSON where I think `foo\\ bar` would be required 🤔 which would interfere with readability.

> This is a major reversal of past choices.
> Can you link to any notes/logs where this was discussed?

+1 to this question—what problems were we running into where whitespace was the problem? I’m not necessarily opposed to the idea, just lacking context that I can’t find in this PR

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


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

Received on Friday, 10 January 2025 16:47:55 UTC