- From: nesquarx via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Jan 2024 14:38:03 +0000
- To: public-design-tokens-log@w3.org
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 Mon, Jan 22, 2024, 1:29 AM Steve Dodier-Lazaro ***@***.***> wrote: > @nesquarx <https://github.com/nesquarx> at the end of the day, yes we'll > have access to arbitrary attributes with no meaning attached. I'm ok with > going down that path and handling the meaning-making of $private myself, > but I believe this ticket is about attributing meaning *in the spec* :) > > — > Reply to this email directly, view it on GitHub > <https://github.com/design-tokens/community-group/issues/110#issuecomment-1903405091>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEKS36BGNH5BUNO54HAK4SDYPYIOBAVCNFSM5NQD7GS2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJQGM2DANJQHEYQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- GitHub Notification of comment by nesquarx Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/110#issuecomment-1904139605 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 January 2024 14:38:05 UTC