Re: [community-group] Native modes and theming support (#210)

Hey, I might have an additional requirement, that is not already really considered, as far as I can tell by briefly reading thru this issue here. 

Currently within my multi-dimensional theming setup with the `$themes.json` file and Style-Dictionary, on important side-effect of the `selectedTokenSets` is that you can control the order of the tokens in the output files with the order of the properties in the `selectedTokenSets` object.

**Why is this important?**
For me this is important cause I can make very precise diffs for each design token release, for each of the permutated output files and for each platform. On the one hand this is a very fast way of communicating in detail which tokens and token values have changed, but also a good test, if changes at the token build pipeline really produce the expected output. If the order changes in the `selectedTokenSets` object between releases, maybe because a designer can't really control that order via the Tokens Studio for Figma Plugin properly in the `$themes.json` file, then the diff for the generated code in the token output files is not very meaningful anymore.

As far as I have read in this documentation here https://resolver-spec.netlify.app/ this topic of the order of the `selectedTokenSets` should be covered by the current draft of the resolver spec. For the sake of bringing all possible requirements to the table, I just wanted to explicitly mention it here as well.

-- 
GitHub Notification of comment by DarioSoller
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/210#issuecomment-2654334488 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 12 February 2025 17:02:08 UTC