refactor(providers): reuse retired Roo identifier - #1166
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe router removal logic now derives the legacy Roo provider identifier from ChangesRoo provider removal
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
src/core/config/__tests__/routerRemoval.spec.tsESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox. src/core/config/routerRemoval.tsESLint skipped: the ESLint configuration for this file references a package that is not available in the sandbox. 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
LEGACY_ROO_PROVIDERreferenceretiredProviderIdentifiers.roo"roo"value and compatibility checksPart of #944 (item 5: reuse the retired-provider registry).
Testing
npx vitest run core/config/__tests__/routerRemoval.spec.ts core/config/__tests__/ProviderSettingsManager.spec.ts core/config/__tests__/ContextProxy.spec.ts(85 tests passed)pnpm --dir src exec eslint --prune-suppressions --max-warnings=0 core/config/routerRemoval.ts core/config/__tests__/routerRemoval.spec.tsSummary by CodeRabbit