test({react,preact}-query/usePrefetchQuery): use the '.then()' convention consistently#11091
Conversation
…tion consistently
|
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 (2)
📝 WalkthroughWalkthroughUpdated React and Preact ChangesPrefetch error test updates
Estimated code review effort: 1 (Trivial) | ~5 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 cb6eb48
☁️ Nx Cloud last updated this comment at |
🎯 Changes
Two
queryFn.mockImplementationOnceoverrides inusePrefetchQuery.test.tsxare still written withasync/await, while the base implementation of the very samequeryFnalready uses.then().#10399/#10400converted themockImplementationof the sharedgenerateQueryFnhelper in these files, so these look like leftovers from that pass , they appear to be the lastmockImplementationOnce(async ...)in the repo.The rejection happens strictly after
sleep(10)resolves, so the timing is unchanged.Would it make sense to switch them to match the convention 🤔
✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit