- From: James Nash via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Feb 2023 23:55:49 +0000
- To: public-design-tokens-log@w3.org
Yup. Your 2nd idea, the `$token` property for groups, is essentially the same as the `$default` one I proposed in this [comment on #97](https://github.com/design-tokens/community-group/issues/97#issuecomment-1012611941). :-) Out of the two, I would prefer that approach for the same reasons you've identified: The "special" group `$token` can have its own token-specific properties independently of its parent group. For example, the group and its `$token` could each have their own description, extensions, etc. -- GitHub Notification of comment by c1rrus Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/135#issuecomment-1419960710 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 February 2023 23:55:50 UTC