Skip to content
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

Offline Support for Version 2? #2460

Closed
ralphchristianeclipse opened this issue Nov 2, 2017 · 9 comments
Closed

Offline Support for Version 2? #2460

ralphchristianeclipse opened this issue Nov 2, 2017 · 9 comments
Assignees

Comments

@ralphchristianeclipse
Copy link

Based on the apollo client v2 redux has been deprecated as the default store

any ideas how to do offline support for apollo client?

@lancygoyal
Copy link

Is there is any way to configure apollo client with redux ?

@2WheelCoder
Copy link

This has been discussed across a couple of other issues here and in apollo-link, notably apollographql/apollo-link#125. I think there's some good momentum to get an offline cache solution going for Apollo 2 and I believe @danieljvdm may be opening a PR. I think other features like queueing requests are probably more suited to an apollo-link alternative or middleware/afterware.

@stubailo @helfer Would a PR adding offline cacheing with something like LocalForage to apollo-cache-inmemory be a welcome feature?

@jbaxleyiii
Copy link
Contributor

@ralphchristianeclipse we definitely want to have great offline support! Its one of the big reasons for the new architecture of the 2.0 🎉

That issue that @2WheelCoder is a great starting point, but we can also have a discussion around features here for everyone to chime in (this repo has higher traffic)

@2WheelCoder I'd prefer that any offline tooling work across cache implementations so maybe it is a wrapper around the Cache API so that other implementations can benefit from it?

@danieljvdm
Copy link
Contributor

@jbaxleyiii I think in order for offline to work across cache implementations we need a cache listener (to know when the store updates, in order to persist) on the top level api. Do you agree with this? If so I can probably get started on a PR for that.

@franceindia
Copy link

👍+1 on this.

@sscaff1
Copy link

sscaff1 commented Nov 15, 2017

This is stopping me from migrating my app to use GraphQL on the client. I still rely heavily on Redux Persist to ensure I have access to my data offline. +1 for this.

@clem109
Copy link

clem109 commented Nov 29, 2017

👍 +1

@stubailo
Copy link
Contributor

We're working on it here, please join in! https://github.com/apollographql/apollo-cache-asyncstorage/issues/6

@hwillson
Copy link
Member

hwillson commented Jul 27, 2018

To help provide a more clear separation between feature requests / discussions and bugs, and to help clean up the feature request / discussion backlog, Apollo Client feature requests / discussions are now being managed under the https://github.com/apollographql/apollo-feature-requests repository.

Migrated to: apollographql/apollo-feature-requests#11

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests