Re: [community-group] Are references generally allowed in arrays? (#241)

As I understand it, it’s the difference from a primitive type (8.x) vs a composite type (9.x). Primitive types may only alias to their own types. A composite type is made up of multiple primitives, and can either alias to their own type, or alias any of their individual parts. I think cubicBezier was considered a primitive type because it gets referenced within a transition type.

My guess is (as I’m guessing) it was considered too complicated to nest number aliases within a cubicBezier within a transition token. I think as-written if a cubicBezier could have internal aliases then it would be reclassified as a composite type (9.x). But would that be bad? I personally don’t know of any downsides. Just seems like it would add more utility, like you said.

I also don’t have full context of why there’s a distinction between primitive and composite types, also; someone else may be able to answer that better. As long as we’re not allowing aliases absolutely _everywhere_ (aliasing part of IDs or substrings would be chaotic IMO), I don’t have any downsides off the top of my head of allowing aliases wherever they seem reasonable.

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


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

Received on Thursday, 15 August 2024 14:12:26 UTC