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

Feature: Client/cache persistence #371

Open
hwillson opened this issue Aug 5, 2021 · 2 comments
Open

Feature: Client/cache persistence #371

hwillson opened this issue Aug 5, 2021 · 2 comments
Labels
📕 cache Feature requests related to the cache

Comments

@hwillson
Copy link
Member

hwillson commented Aug 5, 2021

This issue tracks adding new APIs to facilitate client/cache persistence, providing a way for web/mobile users to save their application state for a defined period of time (and will help make the lives of projects like apollo3-cache-persist easier).

Related: apollographql/apollo-client#7148 (review)

@hwillson hwillson changed the title Feature: Cache persistence Feature: Client/cache persistence Aug 6, 2021
@austinbiggs
Copy link

Is this currently slated for a planned release? 😸

@12dollar
Copy link

Is this currently slated for a planned release? 😸

They are not going to do it if it was even removed from 4.0 release.
I'm migrating away to urql now. Have been waiting way too long that they finally introduce client/cache persistence. I'd propose to do the same for everyone reading this as you can't expect any real progress here.

@alessbell alessbell transferred this issue from apollographql/apollo-client Apr 28, 2023
@alessbell alessbell added the project-apollo-client (legacy) LEGACY TAG DO NOT USE label Apr 28, 2023
@jerelmiller jerelmiller added 📕 cache Feature requests related to the cache and removed project-apollo-client (legacy) LEGACY TAG DO NOT USE labels Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📕 cache Feature requests related to the cache
Projects
None yet
Development

No branches or pull requests

6 participants