Re: [community-group] Proposal: JSON Schema $ref for aliases (breaking change) (#259)

> @drwpow: Proposal: count anything as an alias if a $value of one token points to another token’s $value (which means aliasing the entire token object itself, or a group, means aliases are created)

> @kaelig: The only possible issue is that we'd no longer support "inline aliases" interpolated in a value. For example: `{spacing.inline.small} 1em 0 {spacing.inline.small}`. I don't know if this is a limitation we want to embrace or if there are legitimate use-cases where interpolation is needed. **Editors & community, please advise!**

On this one point I have to say I've resented, in the past, the fact that `.value` gets preferential treatment and that I can't reference an entire subpath of my token tree, or a specific field like a description or attribute. There are relations in my tokens that would allow me to write DRYer code, that I feel I can't express with aliasing being reserved to values.

What I'm saying is very much beside the point of Drew's proposal and bordering on off-topic, but a change of format would be a good time to address this topic if it hasn't already been addressed in prior conversations.

-- 
GitHub Notification of comment by Sidnioulz
Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/259#issuecomment-3244136577 using your GitHub account


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

Received on Tuesday, 2 September 2025 07:33:34 UTC