feat(ui): Productivity pilot reusing the analytics dashboard (U5 B2)#440
Conversation
Third B2 slice — the first to reuse the generic AnalyticsDashboard from #439 with no new libs/ui component: - Electron: pure productivity-ui mappers (formatHours; buildProductivity Kpis/Charts/Sections from ProductivitySummary + ProductivityTrend Point, reusing analytics-ui's formatters/shortDate/sampleLabels/ successRateTone; converts the backend 0-1 rates to whole percents; 7 tests) + ProductivityPilotView over getProductivitySummary + getProductivityTrends. Mounted as "Productivity (new UI)". - i18n: analytics:productivityPilot.* keys (en+fr; the productivity screens share the analytics namespace), navigation.productivityNext. Scope: the productivity mockup's categorical bar panels ("when you ship", "where the time went") have no backing data in the report, so — like the Patterns pilot — this maps only the real data: KPI summary figures + the daily trend series as line charts + outcome/effort cards. No BarChart primitive is invented for panels the backend can't fill. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Warning Review limit reached
Next review available in: 20 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 reviews. How do review 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 refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
✨ 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 |
|



Summary
Third B2 slice, and the first to prove the batch payoff: it reuses the generic
AnalyticsDashboardfrom #439 with no new libs/ui component — just new mappers.Electron
productivity-uimappers:formatHours;buildProductivityKpis/buildProductivityCharts/buildProductivitySectionsfromProductivitySummary+ProductivityTrendPoint, reusinganalytics-ui'sformatPercent/shortDate/sampleLabels/successRateTone(DRY). Backend success rates are 0.0–1.0, converted to whole percents. 7 tests.ProductivityPilotViewovergetProductivitySummary+getProductivityTrends, mounted as "Productivity (new UI)" beside the legacy view.i18n
analytics:productivityPilot.*(en+fr — the productivity screens share the analytics namespace),navigation:items.productivityNext.Scope
The Productivity mockup's categorical bar panels ("when you ship" = hour-of-day, "where the time went" = category) have no backing data in
ProductivitySummary/ProductivityTrendPoint. So — consistent with the Patterns pilot — this maps only the real data: KPI summary figures + the daily trend series as line charts + outcome/effort summary cards. No BarChart primitive is invented to render panels the backend can't fill; if that data lands later, a BarChart primitive + those panels are a clean follow-up.Verification
AnalyticsDashboard(already verified in feat(ui): Analytics dashboard pilot on the shared design system (U5 B2) #439) renders it — no Storybook change.Next in B2
Merge Analytics, then Model Usage (line/sparkline-based, fits the primitives directly).
🤖 Generated with Claude Code