Release 3.7.0 #9633
Merged
Release 3.7.0 #9633
Conversation
This file contains 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
Doing this right would potentially resolve issue #9690.
I could swear I tried this before and it broke a bunch of tests, but tests are passing without it.
…ast.cleanup Replace `concast.cleanup` method with simpler `concast.beforeNext` API
This is just one implementation of a FragmentRegistry that could be provided to InMemoryCache to fill in missing fragment declarations in transformForLink. Learning from past mistakes, we will avoid referring directly to this particular implementation of FragmentRegistry within the InMemoryCache implementation, since that forces the full FragmentRegistry implementation to be bundled even when it is not used.
As long as InMemoryCache uses only this TypeScript interface when handling FragmentRegistry configurations, any implementation can be swapped in without also paying for the bundle size of the default implementation (the FragmentRegistry class).
Since these changes do not include any calls to createFragmentRegistry, the FragmentRegistry class implementation remains optional and thus tree-shakable if unused.
Allow registering named fragments with `InMemoryCache` to support using `...FragmentName` in queries without redeclaring `FragmentName` in every query
#10118) * Improve flaky HoC fetchMore test. * Strengthen flaky useFragment cache.{modify,writeFragment} test.
This is the first "release candidate" for the upcoming 3.7.0 minor release, signalling we will only be fixing bugs and adding missing documentation before the final release. No new features, in other words. Please run `npm i @apollo/client@next` to install this version and kick the tires in your real applications. We appreciate your feedback! 🐣
Deprecates the `onSubscriptionData` and `onSubscriptionComplete` callbacks in favor of the simplified `onData` and `onComplete` callbacks.
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Like the Release 3.6.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.7.0.If you want to test these changes, run
in your application, where the
nin-beta.ncomes from the most recent commit message likeUntil v3.7.0 is released, we can continue merging smaller changes into
mainand releasing them, without worrying about larger changes on therelease-3.7branch.