- From: Drew Powers via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jan 2022 23:46:37 +0000
- To: public-design-tokens-log@w3.org
> Suggestion 2: **Token and group hybrid** This is so interesting to see this suggestion because that exact idea has been something I’ve been mulling about for a while. I posted a [comment in the theme discussion](https://github.com/design-tokens/community-group/issues/2#issuecomment-1011550482) with a similar syntax, but I tried to format it according to previous comments. Here’s one idea for your “hybrid” suggestion but with a syntax I’d prefer: ```json { "color": { "accent": { "type": "color", "value": "#dd0000", "mode": { "light": #ff2222" "dark": "#aa0000" } } } } ``` _Note: `mode` inherits `type` from parent; it must be the same type and each value in the object is essentially another `value`_ By namespacing it under `mode` ([idea](https://twitter.com/bigmediumjosh/status/1450914012036804618)), it hopefully resolves the reserved word issue. And the `type` inheritance hopefully alleviates some complexity. But all just suggestions! I’m sure I’m missing something and there are likely tradeoffs to this idea. -- GitHub Notification of comment by drwpow Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/97#issuecomment-1011554390 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 January 2022 23:46:39 UTC