Uh oh!
There was an error while loading. Please reload this page.
test({react,preact}-query/usePrefetchQuery): inline the 'generateQueryFn' factory into each call site - #11080
Conversation
…yFn' factory into each call site
View your CI Pipeline Execution ↗ for commit fdd34ca
☁️ 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. |
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe React and Preact ChangesusePrefetchQuery test mock refactor
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
size-limit report 📦
|
….fn()' wrapper on the never-asserted sentinel queryFn
Uh oh!
There was an error while loading. Please reload this page.
🎯 Changes
Inlines the
generateQueryFnfactory (used 9 times) directly at each call site asvi.fn(() => sleep(10).then(() => '...')), matching the plain inlinequeryFnstyle used elsewhere in the test suite.vi.fn()is retained (not a bare arrow function) because several assertions depend on it being a spy:toHaveBeenCalledTimes,.mockClear(), and.mockImplementationOnce()to simulate a failed fetch. The explicit generic type parameter on the removed factory wasn't load-bearing —vi.fn(impl)infers the same signature from its implementation. Applies to bothreact-queryandpreact-query.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit
usePrefetchQuerytests with scenario-specific mockedqueryFnimplementations instead of a shared helper.