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
It would be great if comments could be supplied at other levels of the json tree and not just within a property.
Use case:
{
"color":{
"utilities":{
"comment":"Use these colors only when specified in design docs, they are only to be used in specific situations",
"error":{
"value":"red",
"comment":"Use for error text on bg-error"
}
}
}
}
This would than ideally translate to something like this in css and similarly to other languages.
/* Use these colors only when specified in design docs, they are only to be used in specific situations */--color-utilities-error: red; /* Use for error text on bg-error */
Since one of the big benefits of design tokens should be that it brings more documentation to a design system, allowing for more written documentation within the system would be very helpful towards this goal.
The text was updated successfully, but these errors were encountered:
Those would work, except those comments (or any other metadata) would not be reflected in some formats, like css/variables or scss/variables for example. Other than the issue with json/nested (#464 and PR #465 ), the json format will pass that data through to the output. But maybe we could make css/variables and scss/variables output those comments as well.
It would be great if
comments
could be supplied at other levels of the json tree and not just within a property.Use case:
This would than ideally translate to something like this in
css
and similarly to other languages.Since one of the big benefits of design tokens should be that it brings more documentation to a design system, allowing for more written documentation within the system would be very helpful towards this goal.
The text was updated successfully, but these errors were encountered: