fix(query-core): memoize falsy combine results in QueriesObserver#11065
Open
zelinewang wants to merge 1 commit into
Open
fix(query-core): memoize falsy combine results in QueriesObserver#11065zelinewang wants to merge 1 commit into
zelinewang wants to merge 1 commit into
Conversation
Contributor
|
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 (3)
📝 WalkthroughWalkthrough
ChangesQueriesObserver combined-result caching
Estimated code review effort: 2 (Simple) | ~10 minutes 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
QueriesObservertreated a falsy combined result as if no cached resultexisted. A stable
combinecallback returning0,-0,NaN,false, anempty string,
null,undefined, or0nwas therefore called again even whenneither the callback nor any query result had changed.
This removes the value-truthiness check from the cache invalidation condition.
The existing result identity, query hash, and callback identity checks still
perform the initial calculation and invalidate the cache when an input changes.
The cached field now uses definite assignment because
undefinedis itself avalid combined result and cannot serve as an initialization sentinel.
The regression test covers all eight standard primitive falsy values.
Testing
pnpm exec nx run @tanstack/query-core:test:lib --skip-nx-cache -- --run src/__tests__/queriesObserver.test.tsx -t 'should cache the falsy combined result'— 62 tests passedpnpm exec nx run @tanstack/query-core:test:lib --skip-nx-cache— 24 files and 554 tests passed, with no type errorspnpm exec nx run @tanstack/query-core:test:eslint --skip-nx-cache— passed with no errorsgit diff --checkpassedRelease impact
A patch changeset for
@tanstack/query-coreis included.Summary by CodeRabbit
Bug Fixes
false,null,undefined,0, and empty strings.Tests