test(query-broadcast-client-experimental): replace inline query key literals with 'queryKey' in incoming message tests - #11247
Conversation
…iterals with 'queryKey' in incoming message tests
|
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 (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe broadcast error-handling tests now use generated, distinct query keys. They verify incoming messages and later local updates for newly built and existing queries after failures. ChangesBroadcast test recovery
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This test-only change replaces hardcoded query keys and hashes with generated values without changing production behavior; no actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 2a995ab
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version Preview10 package(s) bumped directly, 15 bumped as dependents. 🟨 Minor bumps
🟩 Patch bumps
|
size-limit report 📦
|
🎯 Changes
Replace inline query key literals (
['remote'],['existing'],['local'],['local2']) withqueryKey()from@tanstack/query-test-utilsin the two "incoming message handling" tests added by #11242, soqueryHashvalues are computed from the generated keys (JSON.stringify(remoteKey)for the new/uncached query,existingQuery.queryHashunchanged for the cached one) instead of hardcoded.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit