Milber Ferreira
Milber Ferreira
> Hmm, I'm not sure I see what the benefit would be. Kebab case is invalid syntax in just about every environment _except_ CSS, so to export names for JavaScript,...
Any additional thoughts regarding this?
Can I become part of the spec editors?
@c1rrus Essentially yes, it does that + one more thing: 1. It forces `"option"` and `"alias"` tokens to be explicitly grouped within the token system as clusters. 2. It prevents...
@TravisSpomer Exactly these kinds of issues you talk about are those that will be fixed by adding the "options" and "aliases" clusters with specific rules for each. As mentioned before,...
> What do you see as the difference between a "description" and a "comment"? For example in a "font-size" token, you could add a "$description" for a specific token saying;...
Hi @lauthieb, The example I provided is a very simple one. However, there are plenty of scenarios where you can make a difference between what's communicated in a documentation tool,...
I believe that choosing simplicity is not the right approach when talking about a specification. I would like to hear a better argument before this ticket is closed.
> maybe best to split this in two separate tickets. It's tricky to discuss two questions in a single thread :) Good idea ;) Done, here is the ticket for...
For example, when working with deep-nested alias tokens, tools could expose the `$reference` property (name of the referred token) to the UI to let the user understand token inheritance a...