-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
test(query-core/queryObserver): add test for 'getOptimisticResult' updating 'currentResult' with changed data #10102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
β¦dating 'currentResult' with changed data
|
π WalkthroughWalkthroughThis PR adds a test case to validate that Changes
Estimated code review effortπ― 2 (Simple) | β±οΈ ~8 minutes Possibly related PRs
Suggested labels
Poem
π₯ Pre-merge checks | β 3β Passed checks (3 passed)
βοΈ Tip: You can configure your own custom pre-merge checks in the settings. β¨ Finishing touches
π§ͺ Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution β for commit 717d5d8
βοΈ Nx Cloud last updated this comment at |
π― Changes
Add a test to verify that
getOptimisticResultupdatescurrentResultwhen the query data has changed between renders (e.g., viasetQueryData).β Checklist
pnpm run test:pr.π Release Impact