fix(ic-dashboard): consistent empty-data KPI rendering - #176
Conversation
|
Warning Review limit reached
More reviews will be available in 29 minutes and 21 seconds. Learn how PR review limits work. To continue reviewing without waiting, enable usage-based billing in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthrough
ChangesKpiTile null-value display and dashboard placeholder fallback
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/screens/ic-dashboard/engineering-dashboard-v2.tsx`:
- Around line 86-106: The empty-data KPI path in engineering-dashboard-v2 is
still being rendered as regular KPI tiles, which causes zero-valued metrics and
peer text to appear instead of true empty cards. Update the no-data branch in
the KPI rendering logic around kpiTiles/kpiTileCount to route empty `kpis`
through `KpiTilePlaceholder` rather than `KpiTile`, so the fallback state stays
visually distinct from real KPI content while preserving the existing
`kpiPlaceholders` and `hasKpiData` checks.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 1eac19cd-5ab4-44c1-8b7e-d234512455e9
📒 Files selected for processing (3)
src/components/widgets/v2/kpi-tile.test.tsxsrc/components/widgets/v2/kpi-tile.tsxsrc/screens/ic-dashboard/engineering-dashboard-v2.tsx
Signed-off-by: Aleksandr Barkhatov <pm@aleks.bar>
Signed-off-by: Aleksandr Barkhatov <pm@aleks.bar>
558a588 to
97dcdb9
Compare
Problem
On the IC dashboard, empty-data states render inconsistently:
and hide the peer median whenever the person has no value of
their own — showing "No peer data" even when a cohort median
exists.
top-line KPIs have no data, even with section activity — the page
jumps straight to "Needs attention". The error case already
renders placeholder tiles; the empty case did not.
Fix
not unknown), colored against the peer median like any value;
rate/duration metrics keep "—".
own value.
as the catalog defines them, matching users with ≥1 value.
Closes #1465
Summary by CodeRabbit
New Features
Bug Fixes
0instead of an em dash, while percent/rate metrics continue to show an em dash.