Conversation
Move the Coexistence section out of comparison.md into a dedicated docs/coexistence.md so the "Learn more" link from the VS Code extension lands on a self-contained page rather than a mid-section anchor in a long comparison document. The new page covers what steps aside (R console, plot/data viewers) vs. what doesn't (language server, help viewer), the raven.rConsole.activation setting, and the trade-off between running Raven alone vs. both language servers (correcting the previous guidance that incorrectly said lintr works with r.lsp.enabled off — it doesn't, since lintr diagnostics are provided by REditorSupport's language server). Update all references across docs, README, package.json, and extension source to point to the new file.
- Add why you'd choose Raven alone (temp-file send, Arrow data viewer) - Add why you'd keep REditorSupport (workspace viewer panel) - Invite issues for workspace viewer / lintr integration in Raven - Fix contradictory lintr advice: lintr requires r.lsp.enabled true, not false (it's provided by REditorSupport's language server) - Soften r.lsp.enabled: false to an optional optimization, not a requirement, since running both LSPs is fine
Balance the comparison by adding two new sections listing features REditorSupport has that Raven lacks: Language server: lintr diagnostics, session-aware completions from the live globalenv(). VS Code extension: workspace viewer, htmlwidget/Shiny viewer, R Markdown support, list/environment viewer. Invite issues/PRs for any of these.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (13)
📝 WalkthroughWalkthroughThis PR establishes comprehensive documentation for R-console coexistence with other R-focused VS Code extensions and implements activation gating in the extension UI layer. A new coexistence guide is added, comparison documentation is reorganized, internal links are updated, and VS Code commands and menus are gated behind a context key derived from the resolved R-console activation state. ChangesR-Console Coexistence and Activation Gating
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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 |
Benchmark ComparisonNo A baseline will be created when this branch (or a future PR) is merged to |
Summary by CodeRabbit
New Features
Documentation