Re: [community-group] The $ property name prefix should be unnecessary with a well-structured schema (#225)

> I saw a few arguments pro "hand-editing" or "manual" editing/searching. But in my view, people don't search by the `$value` word (by a generic property name). If in a JSON I need to change the `button-secondary-background` value, I'll search `button-secondary-background` and then I'll look for a `value` property.

That's true, perhaps I'm thinking in terms of the file being overwhelming in some instances. Where if someone new needed to visit this, I could tell them: _you don't need to edit anything except for entries that begin with `$`_. Sure, they'll look for `button-secondary-background` but that may have additional unstructured data in there. I think the `$` does a good job identifying what's important. After all, we're just trying to overload the `button-secondary-background: #0000ff` assignment with more data.

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


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

Received on Tuesday, 15 August 2023 20:52:54 UTC