- From: Matt Ström-Awn via GitHub <noreply@w3.org>
- Date: Tue, 02 Sep 2025 15:29:12 +0000
- To: public-design-tokens-log@w3.org
> I'd personally prefer a breaking change that brings both syntaxes on a feature parity level. @Sidnioulz yeah, I think there's probably a lot of arguments on both sides of this. The proposed `$ref` + JSON pointer syntax gives a common syntax that can replace the syntactic sugar of $extends and curly-brace aliases; I see a future where we might be able to deprecate the syntactic sugar and restrict token authors to $ref + JSON pointers only. Having both in the short/medium term increases tool complexity a bit, but I think it's a necessary evil to atone for the sin of introducing curly-brace aliases in the earliest versions of the draft without the deep thinking that we're doing now. -- GitHub Notification of comment by ilikescience Please view or discuss this issue at https://github.com/design-tokens/community-group/pull/298#issuecomment-3245828616 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 15:29:12 UTC