- From: tryoxiss via GitHub <sysbot+gh@w3.org>
- Date: Mon, 11 Dec 2023 01:57:43 +0000
- To: public-design-tokens-log@w3.org
tryoxiss has just created a new issue for https://github.com/design-tokens/community-group: == Custom Types / Interpritations == You say in [what I believe to be the most recent version](https://design-tokens.github.io/community-group/format/#types), that if no `$type` is set or it does not match one in the spec it should be ignored. If it dosent exist then thats fine, but it would be useful--borderline necesarly for .tokens.json to be a meaningful format--to define custom types. Especially since you explictly mention it being simillar to Java or Typesscript where custom types are a deeply core feature. Maybe a syntax for defining them is too much, or maybe that would work (I don't fully know the goals or state of the project), but some way to allow for non-spec types while still being correct would be useful, such a `"$type": "some-extention:color/hsl"` for example). Some examples of useful types which may not justify being in the spec but would be useful: - weight (e.g., for fonts) - radius (e.g., for borders, etc) - animations ( a composite type of all animation traits) Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/233 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 December 2023 01:57:46 UTC