- From: Ryan Johnson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Jun 2022 22:48:50 +0000
- To: public-design-tokens-log@w3.org
Why not a `$status` field instead?
I can see this being useful to describe a token throughout the entirety of its lifespan (not just during deprecation).
Could start with just a few supported values...
- `experimental`
- `stable` (default)
- `deprecated`
_crude, partial JSON Schema doc to illustrate my idea..._
```javascript
{
"$schema": "http://json-schema.org/draft-07/schema",
"$id": "token",
"type": "object",
"properties": {
"$value": {},
"$type": { "type": "string" },
"$extensions": { "type": "object" },
"$state": {
"type": "string",
"default": "available",
"enum": [
"experimental",
"available",
"deprecated"
]
}
},
"required": ["$value"]
}
```
--
GitHub Notification of comment by CITguy
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/118#issuecomment-1150489490 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 June 2022 22:48:51 UTC