Re: [community-group] Re-evaluate $type resolution order (#189)

Of course the editors will have to weigh in and clarify, but given your example:

```js
{
  "gray": {
    "$type": "color",
    "$value": "#808080"
  },
  "grey": {
    "$type": "dimension",
    "$value": "{gray}"
  }
}
```

The token `grey` has a declared `$type` property, so according to the resolution order, we interpret it as being of type `dimension`. The spec says the value of `dimension` tokens must be a "string containing a number (either integer or floating-point) followed by either a "px" or "rem" unit (future spec iterations may add support for additional units)." So it's not valid after all! I would expect the parser to fail and return something like `error: '{gray}' is not a valid value for type "dimension"`.

As for the question of "should we enable authors to retype tokens" ... I haven't come across a case for allowing retyping, either.

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


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

Received on Wednesday, 30 November 2022 21:05:41 UTC