Re: [community-group] Toughts on the Use of "$" Prefix in the DTCG Token Standard (#240)

Seconding @ddamato, specialness in human review is a big sell for the $ -
and I don't see the $ translating to tokens in CSS or in places where it'll
clash with a JQuery or equivalent.

On Tue, 13 Aug 2024 at 19:28, ddamato ***@***.***> wrote:

> I'm reasonably sure the $ convention used here is based on the variable
> naming convention originating in Sass
> <https://sass-lang.com/documentation/variables/>. The jQuery usage is
> less relevant, as the entire library was meant to exist under that one
> namespace. Design tokens are more closely related to styling variables than
> DOM manipulation. I'm not familiar with RxJS observables, but there will be
> plenty of $ among other languages, just like there is plenty of usage of
> different characters for other reasons. I don't know how the RxJS ecosystem
> clashes with what is expected to be used in this specification.
>
> Regardless of the history, what I find beneficial in the $ prefix here
> has to do with JSON's restrictions. While yes it would be great to have all
> of these enhancements to help the developer experience, the core of the
> specification is expected to align with JSON's limitations, AFAICT. We have
> used _ to denote private because the language used doesn't support the
> concept of private (until it does). This isn't necessarily meant for
> someone to edit in an IDE but for systems to ingest and transform into
> styles.
>
> Further, I find that the $ provides more clarity as a "special" field
> than if special keys were to exist without needing to dive into
> documentation. It should raise the question, "Why do these keys have this
> prefix?" as opposed to if keys look like any other keys. However, given
> that you've raised the idea, I'd like to know what you suggest as
> alternatives, knowing the limitations.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/design-tokens/community-group/issues/240#issuecomment-2286325605>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEKS36BFPO55XINO65KHPA3ZRIGGPAVCNFSM6AAAAABMN2DP72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBWGMZDKNRQGU>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>


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


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

Received on Tuesday, 13 August 2024 14:33:42 UTC