[feature/Apollo] Upgrade to Apollo Client 2.0 #1492
Merged
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
tim-soft
changed the title
|
Weighing some options for logging in development as we can't use redux-logger anymore. I may settle on this one as it's nearly identical to the Apollo 1.x logging output |
|
Thanks @tim-soft |
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.
I thought I'd blow the dust off of the Apollo branch with an upgrade from Apollo Client 1.x -> 2.x
Why upgrade to Apollo Client 2.0??
The biggest change in this PR is that I moved the Apollo Cache out of Redux and into Apollo's
InMemoryCache, eliminating the need for Thunk andcreateHelpers.jswhile also simplifyingcreateApolloClient.Logging and other events related to the GraphQL API are now handled by composable Apollo Links https://www.apollographql.com/docs/link/
@langpavel @koistya @frenzzy