- From: Kyle Wanamaker via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Jul 2022 21:39:23 +0000
- To: public-design-tokens-log@w3.org
> Instead of a boolean flag, $deprecated could just use a string value? The reason for `$deprecated` to be an object is for forward compatibility and for machine readability. One possibility to allow simplicity is for `$deprecated` to be `true` or be an object. Angular's config files work this way. I **do not like** this approach, but prior art does exist. It is simple to parse in Javascript, but much harder in languages with strong, static types. If `$deprecated` is an object, it can be evolved with the spec. If `$deprecated` is a string, there is no way to evolve the field. We'd either have to add more fields, for example, `$deprecated-seeOther`, or re-work deprecation into an object. -- GitHub Notification of comment by KyleWpppd Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/118#issuecomment-1183704688 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 21:39:25 UTC