- From: Travis Spomer via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Oct 2022 15:34:41 +0000
- To: public-design-tokens-log@w3.org
I love the convenience of things like JSON5, but not the prospect of any code that wants to support reading design tokens files also having to include a JSON5 parser package. It also might be impossible right now given the state of JSON5 not (to my knowledge) being standardized or fully open; the spec appears to be MIT-licensed. Maybe this could be accomplished by the spec stating that any conforming parser MAY use the data if it is in a format that is *compatible* with JSON like JSON5 or (shudder) YAML, but only JSON is truly valid. Then token transform tools could ship a JSON5 parser and say that *its* allowed input formats are JSON and JSON5, without requiring that *every* tool also support JSON5. In that case people could use JSON5 whenever all of the tools they plan to use are compatible, but maybe they'd have to convert it to JSON first to use it with something someone threw together on a personal `github.io` page and didn't want to include a JSON5 package. -- GitHub Notification of comment by TravisSpomer Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/175#issuecomment-1295143654 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 October 2022 15:34:42 UTC