- From: William M. Riley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Nov 2021 15:16:51 +0000
- To: public-design-tokens-log@w3.org
A couple other fleeting thoughts I had after I posted the above: - it feels like there is a decision here to be made around inheritance for `type`'s, which if this file assumes implicit inheritance, then this may altogether may be a non-issue. The proposal would need to over communicate that for consumers since inheritance is not built into JSON. A similar argument can be made here for `description` - are we describing the group or passing one value down to the tokens themselves? We need that as a clarifying point. This may be contentious too. - if we do not go inheritance, then a signal that isn't `type` feels necessary. Even if it was plural - `types` - instead of my idea above of `contains`, that feels like it would be helpful. -- GitHub Notification of comment by splitinfinities Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/72#issuecomment-957799244 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:16:53 UTC