- From: Milber Ferreira via GitHub <sysbot+gh@w3.org>
- Date: Sun, 19 Jun 2022 09:34:37 +0000
- To: public-design-tokens-log@w3.org
reblim has just created a new issue for https://github.com/design-tokens/community-group: == Type and Value shpould be required token properties == [3.2 (Design) Token Properties](https://second-editors-draft.tr.designtokens.org/format/#design-token-properties) A concern I have with the current specification is that we are not making the "type" property required. I believe that both the "type" and "value" properties should always be required to avoid tools from having to guess a type based on the grouo type, or higher scopes. Nevertheless, in order for this to work well, we must define our core types more precisely and create a complete list of all possible "primitive" token types. In addition, we could have a "default" type that acts like "any" in TypeScript, to be used if a defined type does not provide enough context for a token. Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/139 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 19 June 2022 09:34:38 UTC