feat(dashboard): set Trip Matching visualization to Stacked Area - #121
feat(dashboard): set Trip Matching visualization to Stacked Area#121anant-shipit wants to merge 1 commit into
Conversation
|
Warning Review limit reached
Next review available in: 50 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ 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 |
Fixes #104
Design Decisions Summary
Grouping & Panel Choice:
Grouped under "Matching Quality", the default timeseries displayed raw counts alongside ratio percentages on the same y-axis scale, severely warping the chart.
Visualization Rationale:
I chose a Stacked Area Time Series. Stacking matched over unmatched trips as filled areas reveals total realtime volume while simultaneously indicating the match proportion. The match ratio was explicitly overridden to render as a distinct line on a secondary right-side y-axis for precise reading.
Go Metric Modifications:
No Go metric types were modified.