Re: [community-group] $deprecated property? (#118)

> With an object, $deprecated could then resemble other objects in the spec.

This I do not really follow :)
Why would `com.my-co.lifecycle` have the need to set `sunset`?

This would just be a vanity alias in this case if the spec only allows `$deprecated` property per token.

-------

A `$description` is interesting but I think it might be easier to implement in tools if `$description` is used (for now) to write extra information like this.

I do agree that an object might be better than a simple flag as this allows for future additions.

```json
{
  "Button background": {
    "$type": "...",
    "$value": "...",
    "$description": "Bright pink background for buttons.\nThis has been deprecated.\nSee : <some link> for more info."
    "$deprecated": {
      "$value": true,
      "$future-thing": "..."
    }
  }
}
```

For now I think it would be best to keep this a bit more simple and keep `$deprecated` or a more general `$state` as flags.

Any extra API will also need corresponding UI in design tools so that people can enter data and will also need to be surfaced by all tools that consume tokens.

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


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

Received on Wednesday, 13 July 2022 06:47:22 UTC