- From: Travis Spomer via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Jul 2022 15:43:20 +0000
- To: public-design-tokens-log@w3.org
One issue I see is that this would only allow you to track changes made in a single tokens file. But let's say you have a global tokens file, and both a light theme file and a dark theme file each with the same tokens defined with different values. (See #2 for lots of examples of how people might do things like this.) Having change history be specific to each file makes it harder to track an update that moves a token from the global file into the theme files, which would touch all three. Tooling could obviously still update the change history for you in all three files, but it seems like it would be a lot easier to browse and understand changes in an external change tracking system like (ugh) Git. -- GitHub Notification of comment by TravisSpomer Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/161#issuecomment-1196928929 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 July 2022 15:43:22 UTC