James Nash

The spec editors have reviewed this issue and, given that there's been no further comments, have decided to close this. We thank you for your suggestion, but will continue using...

If I've understood correctly, your proposal essentially does 2 things: 1. Forces "option" and "alias" tokens to be explicitly partioned within the file 2. Prevents "option" tokens from being exported...

Lots of really interesting suggestions here. Thanks everyone for sharing! I'm not sure if additional types for modified/generated colors is the way to go though. My concern is that might...

You've raised a really interesting point that we've not really addressed at all. In one of our earliest drafts (before it was even public) we were considering some kind of...

To get the ball rolling, I'll outline a workaround and some potential approaches: **Work around** Authors can side-step the issue by not using a group. The example in the issue...

@drwpow: I think the `mode` thing you're proposing could be a good be a solution to theming, dark/light modes, etc. - essentially anything where a single token may have alternative...

@ilikescience So, if I've understood your example you're proposing that we alter the syntax of groups to be more token-like? I.e. rather than just a JSON object where any properties...

@TravisSpomer In light of the recent comments on the reserved words issue (#61), I wonder if combination of the prefix idea there and what you've suggested could work: Let's imagine...

Going slightly (more) off-topic, it occurs to me that it might be nice to for "bare" references to also be usable as a shorthand for creating alias tokens. For example:...

@ilikescience : >I'd love to try and motivate the requirement that tokens and groups should be able to share a name before going deep on solving it - but please...