parag2131 opened a new issue, #36875:
URL: https://github.com/apache/superset/issues/36875
### Bug description
Conditional formatting in Big Number (and similar charts) does not respect
UI Theme tokens defined via THEME_DEFAULT or Theme Administration.
Even when colorSuccess, colorWarning, and colorError are explicitly defined
in the UI theme configuration, selecting success / warning / error in
conditional formatting continues to use Superset’s hardcoded default colors
instead of the themed values.
This creates an inconsistency where:
UI elements follow the active theme correctly
Conditional formatting colors remain unchanged and cannot be themed globally
🔹 Environment
Superset version: 6.0.0
Deployment: Docker
Feature flag enabled:
ENABLE_UI_THEME_ADMINISTRATION = True
Theme configuration example:
THEME_DEFAULT = {
"token": {
"colorPrimary": "#2893B3",
"colorSuccess": "#5ac189",
"colorWarning": "#f4d35e",
}
}
🔹 Steps to reproduce
Enable UI Theme Administration
Define colorSuccess, colorWarning, colorError in THEME_DEFAULT
Restart Superset and verify the theme appears under Settings → Themes
Create a Big Number chart
Add conditional formatting and select success as the color scheme
Observe the rendered color
🔹 Expected behavior
Conditional formatting using:
success
warning
error
should use the corresponding theme tokens:
colorSuccess
colorWarning
colorError
so that dashboard visuals are fully aligned with the active UI theme.
🔹 Actual behavior
Conditional formatting colors:
Ignore UI theme tokens
Continue using Superset’s default hardcoded colors
Cannot be customized globally via themes
🔹 Additional context
UI theming works correctly for buttons, inputs, and layout elements
This appears to be a gap between the Ant Design theme system and legacy /
visualization-level conditional formatting
Related discussions indicate theming coverage is still partial (e.g. SIP-82)
This enhancement would significantly improve brand consistency for themed
Superset deployments.
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev 6.0.0
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [ ] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
