Expand statistics with year-over-year insights and dashboard sparklines - #36
Conversation
Adds savings rate, average booking size, largest expense, a weekday spending pattern, and a this-year-vs-last-year comparison to the statistics page, plus quiet trend sparklines on the dashboard's KPI tiles (sharing the statistics query so navigating between the two pages doesn't refetch). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 16 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
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
/api/statisticsnow also returnspreviousYear,weekday,topExpense, and per-monthtransactionCount.StatTileTrendclient component so the sparkline (which needsrecharts+useId) doesn't forceStatTileitself into a client-only component —StatTileis also rendered directly from the server-renderedapp/t/[slug]/page.tsx, which passes lucide icon components as props that can't cross the server/client boundary.Test plan
npx tsc --noEmit— no errorsnpx eslinton changed files — cleannpm run build— succeeds, including/t/[slug]/t/[slug](public tracker page) renders correctly at runtime after the client/server boundary fix🤖 Generated with Claude Code