Skip to content

fix(ui): theme Data Quality summary widgets for dark mode - #33582

Closed
shah-harshit wants to merge 2 commits into
mainfrom
6539-dq-summary-dark
Closed

shah-harshit wants to merge 2 commits into
mainfrom
6539-dq-summary-dark

Conversation

@shah-harshit

@shah-harshit shah-harshit commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Describe your changes

Dark-mode coverage for the AI-mode Data Quality Summary route (workstream open-metadata/openmetadata-collate#6459, ticket open-metadata/openmetadata-collate#6539).

The AI-mode DQ summary shells (components/observability/DataQuality/*) already use adaptive semantic tokens. The remaining dark-mode gaps were in the shared widgets they embed, which baked compile-time fixed-hex LESS palette vars that cannot follow the theme — so chart backgrounds, status cards, statistic widgets, and the test-case status chart stayed light in dark mode.

Changes

  • Neutral surfaces/borders → semantic --color-bg-secondary_subtle / --color-bg-secondary / --color-border-secondary.
  • Status colors--tw-color-utility-{error,success,warning,blue}-*, which auto-invert in dark (per colors.md §2.7) — mirrors the merged StatusCardWidget precedent. Every status mapping is an exact light-value match, so light mode does not regress.
  • AI dashboard section tint tw:bg-gray-blue-25 (fixed light) → tw:bg-utility-gray-blue-50 (auto-inverting).
  • Already-adaptive utility-gray vars left as-is; categorical chart/status data colors intentionally unchanged.

Files:

  • components/DataQuality/DataQualityDashboard/data-quality-dashboard.style.less
  • components/DataQuality/ChartWidgets/chart-widgets.less
  • components/DataQuality/ChartWidgets/StatusCardWidget/status-card-widget.less
  • components/DataQuality/ChartWidgets/DataStatisticWidget/data-statistic-widget.less
  • components/DataQuality/ChartWidgets/TestCaseStatusAreaChartWidget/test-case-status-area-chart-widget.less
  • components/observability/DataQuality/Dashboard/DataQualityDashboard.tsx

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • token-audit introduces no new violations in the changed files
  • git diff --check clean; prettier clean
  • Visual light/dark QA of the AI DQ summary route — pending (static-only change; LESS var swaps, no logic)

🤖 Generated with Claude Code

RetriggerConfidence Score: 5/5

The PR appears safe to merge; the previous stale-test issue is fully fixed and no new actionable defects remain.

Findings

  1. P1 Dashboard test expectations are stale
Summary

Updates shared Data Quality widgets to use theme-adaptive semantic and utility color tokens, fixing light surfaces and status treatments that remained visible in dark mode.

  • Replaces fixed LESS palette colors across chart containers, status cards, statistic widgets, and test-case status widgets.
  • Changes AI Data Quality dashboard section tints to an adaptive gray-blue utility.
  • Updates the associated unit-test expectations to match the new section classes.

Reviews (2) · Last reviewed commit: "fix(ui): use blue-light token + update s..."

The AI-mode Data Quality summary shells already use adaptive semantic
tokens, but the shared widgets they embed (chart backgrounds, status
cards, statistic widgets, test-case status chart) baked compile-time
fixed-hex LESS palette vars (@grey-26/@grey-9/@grey-2/@grey-50, @Blue-13,
@GREEN-*, @RED-*, @yellow-10, @alert-*) that cannot follow the theme, so
those surfaces stayed light in dark mode.

Swap the fixed palette vars for adaptive tokens:
- neutral surfaces/borders -> semantic --color-bg-secondary_subtle /
  --color-bg-secondary / --color-border-secondary
- status colors -> --tw-color-utility-{error,success,warning,blue}-*,
  which auto-invert in dark (mirrors the merged StatusCardWidget
  precedent). Every status mapping is an exact light-value match, so
  light mode does not regress.
- AI dashboard section tint tw:bg-gray-blue-25 (fixed light) ->
  tw:bg-utility-gray-blue-50 (auto-inverting).

Already-adaptive utility-gray vars are left as-is. Categorical chart/
status data colors are intentionally unchanged.

Refs open-metadata/openmetadata-collate#6539 open-metadata/openmetadata-collate#6459

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

❌ PR checklist incomplete

This PR cannot be merged until the following are addressed on its linked issue:

  • No GitHub issue is linked. Link an issue in the Development section of the PR (or add Fixes #12345 to the description). For a same-org cross-repo issue, add Fixes open-metadata/<repo>#123 to the description.

The fields live on the linked issue in the Shipping project (open the issue → right sidebar → Projects). After you set them, re-run this check (or push a commit) — issue/project changes do not re-trigger it automatically.

Maintainers can bypass this check by adding the skip-pr-checks label.

@github-actions

Copy link
Copy Markdown
Contributor

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

@shah-harshit shah-harshit self-assigned this Sep 18, 2026
@shah-harshit shah-harshit added UI UI specific issues safe to test Add this label to run secure Github workflows on PRs skip-pr-checks Bypass PR metadata validation check labels Sep 18, 2026
Comment on lines +32 to +34
'tw:[&_.status-card-widget-container]:border-0 tw:[&_.status-card-widget-container]:bg-utility-gray-blue-50',
'incident-metrics':
'tw:[&_.custom-chart-background]:border-0 tw:[&_.custom-chart-background]:bg-gray-blue-25',
'tw:[&_.custom-chart-background]:border-0 tw:[&_.custom-chart-background]:bg-utility-gray-blue-50',

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Dashboard test expectations are stale

These section backgrounds now use bg-utility-gray-blue-50, but the existing unit test still requires the removed bg-gray-blue-25 classes for both affected cards. The focused DataQualityDashboard.test.tsx test will therefore fail until both expectations are updated.

@shah-harshit

Copy link
Copy Markdown
Contributor Author

Superseded by #33586, which combines the full Data Quality & Observability dark-mode workstream (#6459) into a single PR. Commits carried over via cherry-pick.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to test Add this label to run secure Github workflows on PRs skip-pr-checks Bypass PR metadata validation check UI UI specific issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant