Uh oh!
There was an error while loading. Please reload this page.
test({react,preact}-query/useSuspenseQuery): assert the 'loading' fallback is rendered when gcTime is 0 - #11076
Conversation
View your CI Pipeline Execution ↗ for commit ea6aaa5
☁️ Nx Cloud last updated this comment at |
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)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughSuspense query tests for React and Preact now assert that the ChangesSuspense fallback tests
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
…lback is rendered when gcTime is 0
ea6aaa5 to
6af990fComparesize-limit report 📦
|
Uh oh!
There was an error while loading. Please reload this page.
🎯 Changes
Adds an assertion right after the initial render that the Suspense
'loading'fallback is shown before advancing timers, inshould render the correct amount of times in Suspense mode when gcTime is set to 0for bothreact-queryandpreact-query. The sibling test in the same file (should render the correct amount of times in Suspense mode, withoutgcTime: 0) already follows this convention; thegcTime: 0variant was missing it.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit