- From: Ryan Johnson via GitHub <sysbot+gh@w3.org>
- Date: Sat, 07 Jan 2023 17:29:21 +0000
- To: public-design-tokens-log@w3.org
I could see this syntax being helpful for _custom_ composite tokens. However, it doesn't provide any additional value for composite types that are already _part_ of the spec. Spec-defined, standard composite token types (e.g., typography, shadow, etc.) _should_ have clearly-defined types for each of their properties. Otherwise, what's the point of defining _any_ composite type in the spec? -- GitHub Notification of comment by CITguy Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/199#issuecomment-1374545547 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 7 January 2023 17:29:23 UTC