- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Dec 2022 16:37:37 +0000
- To: public-design-tokens-log@w3.org
> For this issue, do you think requiring alias tokens to NOT have a type (proposal 1.) solves the issue? It might, but an error handling algorithm would also solve it. I have no opinion or preference on what is best here. What to do in this specific case is just currently unspecified. ----- > Yes, this is an issue that I think we need to dig into in a separate topic. Implicit typing of composite tokens makes sense, but requires a strict definition of all the keys that a composite token may have. In the case of typography, in CSS alone there are 57 properties that can change the way type appears. To make implicit typing work, and to not arbitrarily restrict the use case, we'd need to create and maintain a type mapping for all those properties, plus any additional properties on other platforms that aren't covered by CSS. I am unsure what you mean, can you open a separate issue and elaborate? maybe with some examples? -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/196#issuecomment-1344519185 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 December 2022 16:37:39 UTC