-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
fix: move thenable-recreation into createResult #8169
Conversation
`updateResult` will only be called after a fetch, but when we switch between caches without a fetch, we will only call `createResult`; this fix stops `data` from the queryResult and the `thenable` to go out-of-sync; it's backwards compatible because `updateResult` also invokes `createResult`
@KATT FYI |
☁️ Nx Cloud ReportCI is running/has finished running commands for commit c48a77f. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🥳
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8169 +/- ##
===========================================
+ Coverage 45.41% 62.09% +16.68%
===========================================
Files 200 136 -64
Lines 7456 4757 -2699
Branches 1696 1334 -362
===========================================
- Hits 3386 2954 -432
+ Misses 3694 1563 -2131
+ Partials 376 240 -136 |
updateResult
will only be called after a fetch, but when we switch between caches without a fetch, we will only callcreateResult
; this fix stopsdata
from the queryResult and thethenable
to go out-of-sync; it's backwards compatible becauseupdateResult
also invokescreateResult
fixes #8120