feat: plugins tool, DM tree view, and upgrade impact preview#75
Conversation
|
Warning Review limit reached
More reviews will be available in 44 minutes and 14 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ 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 refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (21)
✨ 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 |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
- New Plugins tool (Alt+G): browse declared/managed plugins, check for version updates with libyear scoring. Three sub-views: Plugins, Managed, Updates. - DM Tree sub-view in Dependencies: shows transitive tree of managed dependencies only via new collectManagedDependencyTree() resolver method (Maven 3 + Maven 4). - Upgrade impact preview in Updates: press 't' to see a before/after tree diff when applying an update. TreeDiff algorithm uses parallel DFS to compare two DependencyTreeModel trees. - Panels override needsTickRedraw() for proper async redraw. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Extract shared updateTypeLabel/updateTypeStyle/formatLibYears to VersionComparator, extract handleSimpleStandaloneEvent to ToolPanel, encapsulate PilotProject plugin fields, and add comprehensive tests for DiffOverlay, VersionComparator, and PluginsTui. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
|
2 participants
Summary
Alt+G): browse declared and managed plugins, check for version updates with libyear scoring. Three sub-views: Plugins, Managed, Updates.collectManagedDependencyTree()resolver method (Maven 3 + Maven 4).tto see a before/after tree diff when applying an update.TreeDiffalgorithm uses parallel DFS to compare twoDependencyTreeModeltrees.needsTickRedraw()for proper async redraw of version resolution results.New files
PluginsTui.java— Plugins tool TUI (3 sub-views, async version resolution, libyear)TreeDiff.java— Tree diff algorithm (~95 lines)TreeDiffTest.java— 6 unit tests for the diff algorithmModified files
PilotProject.java— addedPluginrecord and plugin fieldsPilotResolver.java— addedcollectManagedDependencyTree()andcollectArtifactDependencies()Maven3PilotResolver.java/Maven4PilotResolver.java— implementationsMojoHelper.java— plugin extraction helpersDependenciesTui.java— added DM Tree sub-viewUpdatesTui.java— addedtkey for tree impact previewDiffOverlay.java— addedopenTreeImpact()for colored diff renderingPilotShell.java/PilotEngine.java— wiring and registrationREADME.md— addedpilot:pluginsto goals tableTest plan
./mvnw compile -Bpasses./mvnw test -BpassesAlt+G)t, verify tree impact diff🤖 Generated with Claude Code