- From: Travis Spomer via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Apr 2022 16:58:16 +0000
- To: public-design-tokens-log@w3.org
> Please do better! Apologies; I didn't mean to imply that you were being rude. I hope no one else took it that way. I agree with your central points! Parsing strings to get numbers is d—to use nicer-sounding words, *best avoided*—for the reasons you list and more. But I think it makes the most sense for this spec only since, in my view, this format is already clearly leaning strongly toward human-editable rather than optimizing for machines. We agree on the "best" way, just not the best way for this particular spec. The format's design philosophy is perhaps something that needs to be more explicitly stated. If I've misinterpreted it and this is indeed a format primarily to be edited and read by code, then I will wholeheartedly agree with this issue and give it all my upvotes. -- GitHub Notification of comment by TravisSpomer Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/121#issuecomment-1086137364 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 April 2022 16:58:17 UTC