- There are theme colors {theme/primaryColor}, but they are not applied across components - instead the components are created with their own colors (i.e. Lara/Button/buttonBg). Is there a reason you've split out the colors styles this way? It seems a better way would be to use the theme colors so that if those change, the relevant styles would change. Likewise, there is something like 200 individual colors styles making it very unwieldy (like, why do we have infoMessageIconColor, infoMessageTextColor & infoMessageBorder as separate styles when they are the same color, and why is that color not related to the theme?)
- Likewise, text styles exist for h1> h6, but many of the components are not linked to styles (ex: Advanced card does not have a header or body style, messages are not attached to text styles)
Do you have plans to update the component set to align with actual production styles? if not we'll need to do a lot of refactoring of this library to properly reflect the theme, which means adding any newly released components/updates will be a nightmare.
Also, do you have plans to utilize component properties in the future? In this version, there are over 1000 button variants, which could be easily resolved using component properties. I can do that for our files, but again, that means any future updates will be a nightmare to consolidate so I'm trying to figure out the best path forward.
Please advise.