-
Notifications
You must be signed in to change notification settings - Fork 63
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
Make whitespace invalid in token names #216
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for dtcg-tr ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
This is a major reversal of past choices. |
"$value": 33, | ||
"$type": "number" | ||
}, | ||
"Token cuatro": { | ||
"Token-cuatro": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Token-cuatro": { | |
"token-cuatro": { |
@@ -17,6 +17,8 @@ Note: The `$type` property has been added to ensure this example is valid. Pleas | |||
|
|||
</aside> | |||
|
|||
The name of your design token must not include any whitespace. Otherwise your design token is considered as invalid. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The name of your design token must not include any whitespace. Otherwise your design token is considered as invalid. | |
Design tokens are written in kebab-case. Otherwise your design token is considered as invalid. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be left as is. Kebab-case is only one way of avoiding whitespace... snake_case
or CamelCase
are fine too.
We've decided to consider a token as invalid when its name includes whitespaces.
design-token.md
file