- From: James Nash via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Sep 2021 23:40:46 +0000
- To: public-design-tokens-log@w3.org
I'd say a token's value can potentially be any of the JSON types (also including `boolean` and `null`). Of course, each of the DTCG types we define in our spec (`color`, `dimension`, `duration`, etc.) specifies exactly how values of that type must be formatted. So, when using those types (which I suspect most tokens would), we are narrowing down which underlying JSON type(s) those values can be. E.g. `color` values can only ever be JSON strings. However, types we add in future and/or iterations of the current types may well be built on the full range of JSON types, so I see no reason to artificially limit their use. Besides, this rule from the [Types section](https://design-tokens.github.io/community-group/format/#types) pretty much necessitates all JSON types being available: >If the type property is absent, tools MUST treat values as one of the basic JSON types and not attempt to infer any other type from the value. -- GitHub Notification of comment by c1rrus Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/58#issuecomment-918665092 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 September 2021 23:40:48 UTC