Skip to content

Commit

Permalink
feat: add specificity to token types. closes #58 (#71)
Browse files Browse the repository at this point in the history
  • Loading branch information
kevinmpowell committed Sep 17, 2021
1 parent 37bab52 commit cca6827
Showing 1 changed file with 12 additions and 3 deletions.
15 changes: 12 additions & 3 deletions technical-reports/format/design-token.md
Expand Up @@ -23,9 +23,18 @@ The example above therefore defines 1 design token with the following properties

Name and value are both **required**.

<div class="issue" data-number="58" title="Token value data types">
JSON can support string, number, array, and object value types. Should all of these types be allowed for token values?
</div>
### Token value type

Token values may be any valid JSON type:

- `string`
- `number`
- `array`
- `object`
- `boolean`
- `null`

Additionally, tokens may be defined with a more specific [Token Type](#types)

<div class="issue" data-number="55" title="Object vs Array">

Expand Down

0 comments on commit cca6827

Please sign in to comment.