-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Release 3.4.0 #7399
Release 3.4.0 #7399
Conversation
de78a83
to
57a6b9e
Compare
This comment has been minimized.
This comment has been minimized.
@benjamn I get an error when update from This file is: https://github.com/graphql/graphql-js/blob/v15.2.0/src/jsutils/instanceOf.js#L14 All works if I go back to I'm using the @web/dev-server. |
@benjamn I add the npm dependencies diff about #7399 (comment): This downgrade makes the project work again. |
@abdonrd Thanks for the heads up! Just linking to my comment on your issue for others' benefit: #7895 (comment) |
f7caa87
to
4420c49
Compare
@StephenBarlow Looking at the |
@benjamn You mean in the autogenerated reference, yes? I fear I know very little about its internal workings, and it predates me. My guess would be that doing something about this would require an amount of work similar to either:
Both of which feel preferable to tacking features onto our existing solution, which as I understand it is creaky |
Previously, removing an optimistic EntityStore layer with removeOptimistic would dirty all fields of any StoreObjects contained by the removed layer, ignoring the possibility that some of those field values might have been inherited as-is from the parent layer. With this commit, we dirty only those fields whose values will be observably changed by removing the layer, which requires comparing field values between the layer-to-be-removed and its parent layer.
Following a suggestion from @bennypowers in this comment: #7895 (comment)
…uery Optional chaining on usequery
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.
WOOHOO!!! 🎉 🎉 🎉
@abdonrd You have uncanny timing! The final |
Like the Release 3.3.0 PR, this PR will serve to collect significant new features, deprecation warnings, and minor breaking changes that we intend to release in
@apollo/client@3.4.0
.If you want to test these changes, run
in your application, where the
n
in-beta.n
comes from the most recent commit message likeUntil v3.4.0 is released, we can continue merging smaller changes into
main
and releasing them, without worrying about larger changes on therelease-3.4
branch.