- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Jul 2022 20:47:44 +0000
- To: public-design-tokens-log@w3.org
> A description and a deprecation notice are separate concepts, IMO. Consider [@deprecated in Javadoc] True. Instead of a boolean flag, `$deprecated` could just use a string value? If it's there, the token is deprecated and the string contents is the deprecation message. ------- So to summarise we have expanded from a need to set a `deprecated` boolean flag to these concerns/requirements : - record (complex) lifecycle states per token - different teams might have different conventions for these states - from a spec and tooling perspective it is still best to standardise around a fixed set of states - being able to extend these states via `$extensions` would be good - add descriptions/messages to accompany states -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/118#issuecomment-1183662921 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 20:47:45 UTC