- From: Ivan Maksimovic via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Nov 2021 15:39:39 +0000
- To: public-design-tokens-log@w3.org
Additional `tokens` node is just one suggestion, but it fully solves the problem of reserved words and collisions, both today and in future. At least I didn't find a case when this would not work. I would also argue that having tokens under `tokens` node increases readability, not decrease. Prefixes are also solving the problem and the only con I see is ease of access if prefix is `$`. Some other prefix might avoid that issue. But which one? Is this worth discussing more? Maybe the readability is decreased, but with "the right" prefix, it might also increase readability it and make it easy to differentiate tokens from groups and other properties. Current proposal with 4 reserved keywords is ok today, but I am pretty sure that it will not be enough as the project matures. Then the choice will be either breaking change, which is IMO a huge deal in projects like this, or some hacky solutions where everything is for example added to `extensions` just to avoid breaking change. Given the impact of these decisions, I would like to ask you for a bit more discussion, both around possible prefixes, additional node, and impact of breaking change if a new reserved word is added later. -- GitHub Notification of comment by ivnmaksimovic Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/61#issuecomment-957847793 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 November 2021 15:39:41 UTC