-
-
Notifications
You must be signed in to change notification settings - Fork 626
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
Result Context, watchMutation, CacheRereadPolicy #795
Conversation
BREAKING CHANGE: By fixing the defaults for mutations, the old behavior is now lost
Codecov Report
@@ Coverage Diff @@
## beta #795 +/- ##
==========================================
+ Coverage 49.52% 49.74% +0.22%
==========================================
Files 35 35
Lines 1357 1389 +32
==========================================
+ Hits 672 691 +19
- Misses 685 698 +13
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
🎉 This PR is included in version 4.0.0-beta.7 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 4.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Closes #793
Closes #774
Breaking changes
Mutation
behavior, which can be regained by overridingDefaultPolicies.watchMutation
.Fixes / Enhancements
Mutation
behavior by introducingwatchMutation
, which should mitigate the problems in mutations through watchQuery use cacheAndNetwork, which yields unexpected results #774CacheRereadPolicy
for controlling normalized re-reads and rebroadcast behavior more granularlyresponse.context
toQueryResult
(Make QueryResult include context #793)QueryResult.unexecuted
singleton for unexecuted mutationswatchMutation
default policies are the same asmutation
:the old behavior can be regained via
Docs
CacheRereadPolicy
andwatchMutation