Uh oh!
There was an error while loading. Please reload this page.
test(svelte-query/createQuery): replace 'toBeDefined' with exact-value assertion - #11126
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 (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe query client switching test now verifies that cached entries retain the expected ChangesQuery client cache validation
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 d279a2a
☁️ Nx Cloud last updated this comment at |
Uh oh!
There was an error while loading. Please reload this page.
🎯 Changes
Continues the recent test-quality series (e.g. #11105, #11093, #11124) by converting the toBeDefined() assertion in svelte-query tests to an exact assertion:
createQuery.svelte.test.ts— the cache presence checks now assert the exactqueryKey(?.queryKey) registered in each client's cache, confirming that the query is correctly re-registered under the new client after the reactive swap fromqueryClient1toqueryClient2.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit