nesquarx

It's true trying to introduce logic is a slippery slope. But similar to themes we can have 'flags' which can change values by their presence, and said flags can be...

If alias and extends are token and group level keywords for the same activity. Would it decrease or increase confusion to have a single keyword for it? On Tue, 29...

Ah, then keeping them distinct makes sense. On Fri, 1 Apr, 2022, 4:31 pm Joren Broekema, ***@***.***> wrote: > I think the behavior is a bit more complex on token...

I would also prefer a more future-proof spec that can default/fallback to hex today while allowing for other color spaces/processes to be used tomorrow. That is what CSS itself is...

Even font family or size could be inherited. On Thu, 29 Sep, 2022, 1:08 pm Lukas Oppermann, ***@***.***> wrote: > One approach to this problem is to allow composite types...

I know color and type are the main use cases, I'll just be a bit more generic in my description. I'm repeating some stuff from previous comments. Here's my ideal...

I believe a simple $meta array variable which can classify tokens for categorizing, processing and extraction purposes would suffice any needs. For example $meta: ["private", "internal", "debug", "lightThemeOnly"]; Or whatever...

Agreed, if the most common cases call for $private, having it makes sense, but trying to increase the scope there instead of an additional generic solution might become exhausting. On...

Empty groups can be placeholders, I've used one as an alias for the default set with no modification, also for planned future updates. Wouldn't want it to throw an error....

We define colors today as an OKLCH value if supported and failing that a hex value... How would we expect to implement this? Especially where the OKLCH does give more...