- From: Kevin Powell via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Nov 2021 14:02:45 +0000
- To: public-design-tokens-log@w3.org
I'm not keen on the `$` prefix or the addition of a `'tokens'` node. Both decrease readability IMO, and the `$` creates the access issues @c1rrus noted. I think documenting our current reserved words and having a rule in the spec that a token cannot be named: * "value" * "description" * "extensions" * "type" is reasonable. If we need to add new reserved keys in the future we can circulate those in the community to gauge the level of collision. It does mean future versions of the spec that add new reserved keys would be breaking changes, which is a bummer, but my gut says we're over engineering this if we're trying to avoid those collisions already. -- GitHub Notification of comment by kevinmpowell Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/61#issuecomment-957643726 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 14:02:47 UTC