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
Hi there, I love the concept of VueDS. I started using it and changing tokens. I found that when colors are being changed and renamed the docs crashed, because the color tokens aren't there anymore in the elements using tokens (buttons, links, etc). In order for this to work currently I would have to go to each component that is using a certain old color token which a priori is unknown for the user of the vueDS.
Ideas for solutions:
Automate with sass placeholder colors
Is there a way to use some sass function that handles this and replaces none found colors with for instance black, white and grey colors, perhaps also some red and not good looking combinations so that the user knows which elements to update?
Another approach to make the vueDS boilerplate more customizable is to name the color tokens with standard names such as primary, secondary, or 1,2,3. I still like the idea of giving names to colors in the palette, but maybe names for the palette can be different than naming convention for the css.
The text was updated successfully, but these errors were encountered:
Hi there, I love the concept of VueDS. I started using it and changing tokens. I found that when colors are being changed and renamed the docs crashed, because the color tokens aren't there anymore in the elements using tokens (buttons, links, etc). In order for this to work currently I would have to go to each component that is using a certain old color token which a priori is unknown for the user of the vueDS.
Ideas for solutions:
Automate with sass placeholder colors
Is there a way to use some sass function that handles this and replaces none found colors with for instance black, white and grey colors, perhaps also some red and not good looking combinations so that the user knows which elements to update?
Use name conventions like bulma
Another approach to make the vueDS boilerplate more customizable is to name the color tokens with standard names such as primary, secondary, or 1,2,3. I still like the idea of giving names to colors in the palette, but maybe names for the palette can be different than naming convention for the css.
The text was updated successfully, but these errors were encountered: