- From: Nico André via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Sep 2024 16:09:33 +0000
- To: public-design-tokens-log@w3.org
> Your suggestion to have a mapping slightly slows down the parsing and at least for me is less readable Agreed on that part @doozMen. I do not completely buy this rationale neither. > is there an issue I can track to when this mapping description lands in the spec I guess the current state is the following: - For primitives (like color, dimension…), they can be aliased by their own type only - even though this information is not written down. - For composites, the mapping is described within the spec already - [border example](https://tr.designtokens.org/format/#border) -- GitHub Notification of comment by nclsndr Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/236#issuecomment-2341380053 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 September 2024 16:09:34 UTC