Re: [community-group] Shadow type feedback (#100)

> how a CSS translation tool might need additional information to decide which CSS property to output?

This is the heart of the issue I guess, and what I'm wondering too. 

So let's say that with the current spec some of the keys are optional.

```json
{
   // box-shadow intended
  "small": {
    "$type": "shadow",
    "$value": {
      "inset": true,
      "offsetX": "0px",
      "offsetY": "1px",
      "blur": "2px",
      "spread": "0px",
      "color": "#ccc"
    }
  },

  // box-shadow intended
  "small": {
    "$type": "shadow",
    "$value": {
      "offsetX": "0px",
      "offsetY": "1px",
      "blur": "2px",
      "spread": "0px",
      "color": "#ccc"
    }
  },

  // drop-shadow intended
  "small": {
    "$type": "shadow",
    "$value": {
      "offsetX": "0px",
      "offsetY": "1px",
      "blur": "2px",
      "color": "#ccc"
    }
  },

  // text-shadow intended
  "small": {
    "$type": "shadow",
    "$value": {
      "offsetX": "0px",
      "offsetY": "1px",
      "blur": "2px",
      "color": "#ccc"
    }
  }
}
```
If we only have one `shadow` `$type`, how would a translation tool be able to determine the output?
Through `$extensions`?   
In the `box-shadow` case missing keys could probably be filled with `0px`, but feels a bit fragile, and doesn't cover all other formats. 
Sorry, bringing more questions here and not much solutions for the moment :sweat_smile: 



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


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

Received on Tuesday, 18 October 2022 11:05:06 UTC