- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Sep 2022 08:00:06 +0000
- To: public-design-tokens-log@w3.org
> In any case, I feel like the existing spec could handle the proposed approach by using a custom entry on the $extensions property. https://tr.designtokens.org/format/#extensions > In order to maintain interoperability between tools that support this format, teams and tools SHOULD restrict their usage of extension data to optional meta-data that is not crucial to understanding that token's value. Using `$extensions` for this use case is discouraged by the spec. It should be solved with multiple files or in the spec itself. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/169#issuecomment-1246390060 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 September 2022 08:00:08 UTC