- From: Kevin Powell via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Sep 2021 12:19:59 +0000
- To: public-design-tokens-log@w3.org
@c1rrus you raise a lot of interesting points here. I think some of which could be moved to the newly created #72 to discuss file & group-level properties. My preference is to only support object style tokens. The "documentation sorting" use case doesn't rank high enough in my mind to add the additional complexity to support arrays in the spec. Having two syntaxes to support will be challenging to document, and challenging for vendors to implement. If we need to solve a "sorting" use case, then I propose a "sortOrder" token property that could be added at any level. (I'm not convinced we need this). I think documentation/sorting use cases can be handled within tools. For example something like Figma could have toggles to let you sort colors by brightness, alphabetically by name, or by opacity. A doc tool could do the same. If there are other use cases that justify preserving order in the actual spec I'd like to understand those. -- GitHub Notification of comment by kevinmpowell Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/55#issuecomment-919096477 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 September 2021 12:20:01 UTC