Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: TanStack/query/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (14)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughDevTools now provides selection state, panel width, offline status, and cache subscriptions through contexts. Full and embedded DevTools trees mount the providers. Tests cover state and subscription isolation across instances. ChangesDevTools state and subscriptions
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The change isolates DevTools state and subscriptions between instances, with regression coverage for isolation and cleanup. No actionable merge-blocking issue is established; merge after normal checks pass. Security Architecture ReviewSecurity architecture risk: ⚪ Minimal · up to The reviewed changes improve instance isolation and cleanup without expanding the data access or control available to DevTools. Shared online managers remain shared intentionally. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
Resilience and Maintainability Implications
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 12 functions across 13 files. (1 skipped: 1 unsupported.)
✨ 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 |
|
View your CI Pipeline Execution ↗ for commit 58685f3
☁️ Nx Cloud last updated this comment at |
🎯 Changes
Solves #9681
Each instance of DevTools now isolates signals to that instance instead of declaring them on the module level, creating signals on the module level that are shared across all instances.
This breaks scenarios where you need to be running two instances of query DevTools alongside each other.
I've broken the state up into three different providers and contexts:
DevtoolsStateProvider: grouped together 3 signals and puts there accesscors and setters into contextDevtoolsOfflineProvider: groups the offline signal with the effect that subscribes to the passed inonlineManagerfrom QueryDevtoolsSubscriptionsProvider: manages the two maps of subscriptions to queries and mutations.And regression tests have been added as well.
Better diff viewer: https://diffshub.com/TanStack/query/pull/11799
Edited reproducer from the issue: https://stackblitz.com/edit/tanstack-react-query-dev-tools-issue-fvstvhn8?file=package.json,src%2FApp.tsx
✅ Checklist
pnpm run test:pr, or these tests do not apply to this pull request.🚀 Release Impact
Summary by CodeRabbit