feat(wiki): render wiki group on unified metric-results#204
Conversation
Flip the wiki dashboard group from the legacy bullet path to a unified collection — pages-created / edits / comments preview, plus a pages-created + edits timeseries drilldown — and strip the wiki legacy plumbing (bullet sections, metric-order, registry ids, catalog prefix). With no legacy groups left, gate the team bullet batch on a non-empty section set: a disabled query stays "pending" forever, which would hang the team view's loading gate, and it would otherwise fire an empty batch on every load. Closes constructorfabric/insight#1705 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Aleksandr Barkhatov <pm@aleks.bar>
|
Warning Review limit reached
Next review available in: 33 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 Run ID: 📒 Files selected for processing (11)
✨ 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 |
ktursunov
left a comment
ktursunov
left a comment
There was a problem hiding this comment.
Please improve coverage
Unit-test isTeamBulletSectionId. The legacy team-bullet wiring (LEGACY_GROUP_IDS map/filter, LEGACY_GROUP_FEEDS, the legacy error branch) is inert with no kind:"legacy" group left, so mark it v8-ignore rather than test-force a legacy group that cannot occur in the shipped config. Clears the diff-coverage gate. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Aleksandr Barkhatov <pm@aleks.bar>
2 participants
Cut the wiki dashboard group over to the unified
/v1/metric-resultspath, mirroring the git/collab/task cutovers. Wiki was the lastkind:"legacy"group.What
kind:"metrics"with aWIKI_COLLECTION(period/peer for all four; timeseries on pages-created + edits), a 3-metric preview (pages created / edits / comments), and a pages-created + edits timeseries drilldown.ic-dashboard.ts,team-view.tssection,metric-order/bullet-defsentries, thewiki_bullet_rowscatalog prefix, and theIC/TEAM_BULLET_WIKIregistry ids (their UUIDs collide with the survivingV2_MEMBER_VALUES_*— those are untouched).pendingforever, which would hang the team view's loading gate; it also avoids firing an empty batch on every load.Backend: constructorfabric/insight#1812.
Safety
New-FE + old-BE degrades to a wiki-card error only; the rest of the dashboard is unaffected. No KPI change (wiki isn't in the KPI row); no heatmap/dept feed for wiki.
Verification
tsc -b(real typecheck),eslint --max-warnings 0,vitest— 312/312./v1/metric-results.Closes constructorfabric/insight#1705
🤖 Generated with Claude Code