- From: James Nash via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 Mar 2024 16:56:41 +0000
- To: public-design-tokens-log@w3.org
c1rrus has just created a new issue for https://github.com/design-tokens/community-group: == Be explicit about whether or not empty groups are allowed == Currently, the spec says nothing about whether or not groups can be empty - i.e. not contain any tokens or nested groups. I've always assumed they _can_ be empty. But [I recently discovered that Cobalt UI has taken the opposite view](https://github.com/drwpow/cobalt-ui/issues/206) and throws an error when it encounters an empy group. The spec doesn't say anything, so neither view is right or wrong. I propose we take a stance on this and be explicit in the spec. Otherwise, differing interpretations will lead to interoperability issues between tools. My vote would be to permit empty groups. While they may seem useless they also do no harm. It's something that teams may legitimately encounter while (re-)organising their tokens and working with work-in-progress DTCG files (that's how I encountered that scenario anyway). Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/235 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 4 March 2024 16:56:43 UTC