You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it's great that these alternative formats are supported, but vanilla JSON still seems to be the most popular format for storing tokens. As a developer, it's the format I'm most comfortable with. But, I'd really like to be able to add comments to my token files. There's a format that would make that possible: JSONC, aka "JSON with Comments".
Using JSONC, this would be possible:
{"color": {"font": {// Colors used for text on a light background"base": {"value": "#111111"},"secondary": {"value": "#333333"},"tertiary": {"value": "#666666"},// Colors used for text on a dark background"inverse": {"base": {"value": "#ffffff"}}}}}
The JSONC format is very popular. There's even built-in syntax support in VS Code:
In short, I think JSONC would be a perfect format for tokens. 😄
The text was updated successfully, but these errors were encountered:
Currently, style-dictionary supports JSON5 for token files (PR: #165). JSON5 is used in the transitive-transforms example "so that it can be marked up with comments for reference." YAML is also supported, and has its own example project.
I think it's great that these alternative formats are supported, but vanilla JSON still seems to be the most popular format for storing tokens. As a developer, it's the format I'm most comfortable with. But, I'd really like to be able to add comments to my token files. There's a format that would make that possible: JSONC, aka "JSON with Comments".
Using JSONC, this would be possible:
The JSONC format is very popular. There's even built-in syntax support in VS Code:
In short, I think JSONC would be a perfect format for tokens. 😄
The text was updated successfully, but these errors were encountered: