-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
Support Apollo Client v3 #1380
Comments
Looks like allot of progress has been made over at https://github.com/apollographql/apollo-client/blob/release-3.0/ is this sufficient to start implementing 3.0? |
I'm working on it here #1383. I think it's fairly stable to start using Apollo Client v3. You can expect an alpha release this weekend. |
Any chance that the observable variables from v1 that were dropped in v2 (#425) might get re-implemented for v3? :) |
Interesting update with the caching system, might be interesting to see how it fits with angular wrapper: apollographql/apollo-feature-requests#5 |
Is this package still actively maintained? |
@Eraldo is Apollo Client v3 out already? Once it's out, there will be a major version of Apollo Angular too |
I am super glad to hear that. |
Apollo Client 3.0 has been officially released now 🎉 Blog Announcement Pleased to hear that there will be a new version of Apollo Angular, will be great to have access to the new caching features. |
@kamilkisiela is #1383 able to be merged or will a new PR be needed? |
The Apollo team published Apollo Client 3.1 today. Any timeline for an Apollo Angular release supporting v3? |
There is a PR open that supports AC3 (now released as apollo-angular@2.0.0-beta.3) here: #1383 Please help testing it and giving feedback if you can! @KeithGillette @charsleysa |
@kamilkisiela it looks like you forgot to push the tag for |
@intellix |
Tried updating and fixed all of the type errors but just ended up with a WSOD (White Screen of Death) with the tab freezing with 150% CPU and was unable to even profile why. Guess I'll wait for other people to try it out |
Also interested in this. This as a feature that allows me to workaround this bug: apollographql/apollo-client#6760 basically 'cache-and-network' fetchpolicies now do a network request everytime something updates the query. I have a page where I do a few local mutations and update a query. This then gets overwritten by the network request data coming in. edit: nvm, a |
No description provided.
The text was updated successfully, but these errors were encountered: