Problem
Theming structure should be more granular by targeting element structure like, tab states, input element states etc.
Expected behavior
The current theme mappings are reflecting to so many places with same values. For example, form fields are using button's default color. To allow better handling of the themes by the consumer for each individual element we need to extend the theming structure. However, the new theming structure should still keep the old values to avoid backwards incompatibility.
Expected steps
- Create the new theming structure in component level
- Multi-State Inputs' active/in-active/disabled state border, foreground and background
- Textual Inputs' active/in-active/disabled state border, foreground and background
- Tabs active/in-active state border, foreground and background
- Button's active/in-active/disabled/status state border, foreground and background
- Prompt card border, foreground and background
- Filled card border, foreground and background
- Global border, foreground and background
- Add additional ones if there are any...
- Assign old (currently used values) to the new theming colors.
- Update the theme-builder with new values (for custom theme building).
Problem
Theming structure should be more granular by targeting element structure like, tab states, input element states etc.
Expected behavior
The current theme mappings are reflecting to so many places with same values. For example, form fields are using button's default color. To allow better handling of the themes by the consumer for each individual element we need to extend the theming structure. However, the new theming structure should still keep the old values to avoid backwards incompatibility.
Expected steps