- From: Travis Spomer via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Oct 2022 05:31:35 +0000
- To: public-design-tokens-log@w3.org
Your comment in #120 has successfully convinced me that the JSON primitive types are actually good and useful! 🙂 But it does still seem likely to me that the vast majority of tokens without a `$type` explicitly present will be mistakes—in fact, your comment has convinced me of that even more. And allowing `$type` on groups to cascade down to the tokens within makes reading token files more complicated and annoying for both humans and code. What we get in exchange is saving a person hand-writing token files a few characters of typing, and if the main use of those primitive types is for extensions (which we hope are not too common), then those savings would be both small *and* rare. So then it seems like there are two major cons to `$type` being optional and one minor pro. That's a bad tradeoff so I'm still strongly in favor of `$type` being required always. -- GitHub Notification of comment by TravisSpomer Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/173#issuecomment-1279666455 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 October 2022 05:31:37 UTC