You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:09:11 UTC
Re: [D] Conditional formatting logic - Why do empty cells get max-opacity color? [superset]
GitHub user dosubot[bot] edited a comment on the discussion: Conditional formatting logic - Why do empty cells get max-opacity color?
<!-- Answer -->
This happens because the conditional formatting logic treats null or empty cells as numeric zero when applying rules like `< 10`, so they end up matching the condition and get highlighted—often with full opacity, making them visually dominant. The code doesn't explicitly exclude nulls from numeric comparisons, so they pass through as if they were `0` and receive the strongest color intensity by default. There’s no built-in config to change this behavior right now, which is why empty cells can be more prominent than actual data matches [[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/packages/superset-ui-chart-controls/src/utils/getColorFormatters.ts#L31-L220)].
Recent updates added a "Use gradient" toggle, letting you switch between gradient (varying opacity) and solid (full opacity) color modes, but this doesn’t address the logic for nulls matching numeric conditions [[source](https://github.com/apache/superset/pull/36280)]. There’s also a new feature for boolean conditional formatting with explicit `isNull` and `isNotNull` operators, so you can intentionally highlight empty/null cells if you want—but by default, nulls are still treated as `0` in numeric rules [[source](https://github.com/apache/superset/pull/36338)].
To align with database semantics (`NULL < 10` should be false), the logic would need to skip null/empty values in the comparator functions. This would require a code change in the conditional formatting utilities (e.g., in `getColorFormatters.ts`). As a workaround, you could use the new boolean operators to target nulls directly, or adjust your data to avoid nulls where possible.
If you want to see this fixed, the best approach is to update the comparator logic to treat null/empty as non-matching for numeric rules, or add a config option to control this behavior. For now, the only way to avoid the visual distraction is to use the boolean formatting or preprocess your data.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=9488969c-b1a1-4b75-a530-9ab0dee0ea55) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/36812#discussioncomment-15327307
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org