Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Types / Interpritations #233

Open
tryoxiss opened this issue Dec 11, 2023 · 0 comments
Open

Custom Types / Interpritations #233

tryoxiss opened this issue Dec 11, 2023 · 0 comments

Comments

@tryoxiss
Copy link

You say in what I believe to be the most recent version, 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant