Re: [community-group] Specification / recommendation for custom types (#223)

• From: Travis Spomer via GitHub <sysbot+gh@w3.org>
• Date: Fri, 14 Jul 2023 18:46:44 +0000
• To: public-design-tokens-log@w3.org
• Message-ID: <issue_comment.created-1636263381-1689360402-sysbot+gh@w3.org>

It's my understanding that the recommendation for custom types would be that you use one of the existing types as the `$type` and then add additional identification necessary as an `$extension`.

```json
{
  "MyBlendingModeToken": {
    "$type": "string",
    "$value": "subtract",
    "$extensions": {
      "com.example.extendedtype": "blendingMode"
    }
  }
}
```

That's how you would do it now—there are other issues open that propose various ways of formalizing custom types so that tools that have never heard of `com.example.extendedtype` would still know its allowed values and format.

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


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

Received on Friday, 14 July 2023 18:46:45 UTC