Re: [community-group] [Format] Token types - optional or required (#63)

To elaborate more on the point I made above, making types required will set an expectation that any tool using the spec will have types present and to make better decisions on how to use the value. Whether that's transforming them to other formats, like the Style Dictionaries and Theos, displaying them in documentation, etc. 

From the example above, the tool can expect `#00000` to be a `Color` and nothing else. It doesn't have to make its own guess at what the intent of the value is.

That seems like a good precedent to set early.

-- 
GitHub Notification of comment by mattfelten
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/63#issuecomment-916517474 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 9 September 2021 23:55:07 UTC