test(solid-query/useQueries): add test for using a provided custom 'queryClient'#10952
Conversation
|
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 (1)
📝 WalkthroughWalkthroughA single test file is updated: ChangesCustom queryClient test for useQueries
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 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)
Comment |
|
View your CI Pipeline Execution ↗ for commit 4e6c0e1
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
size-limit report 📦
|
🎯 Changes
react-query'suseQueriestests cover passing a customqueryClientas the second argument (instead of relying onQueryClientProvider), butsolid-queryhad no equivalent. This ports that coverage.useQueries(() => ({ queries }), () => queryClient)with the client passed directly as the second argument, renders without aQueryClientProvider, and asserts the query resolves against that client.The test passes against the current behavior — no source changes.
✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit