From 3e932389398624cbb74c2b453c6faa1423ebcf9d Mon Sep 17 00:00:00 2001 From: Alagu Selvan <34230909+AlaguSelvan@users.noreply.github.com> Date: Wed, 29 Mar 2023 19:50:58 +0530 Subject: [PATCH] Fixed Typo of library (#10668) * Fix the Typo "Apollo-3-cache-persist" to "Apollo3-cache-persist". Co-authored-by: Alessia Bellisario --- docs/source/local-state/managing-state-with-field-policies.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/local-state/managing-state-with-field-policies.mdx b/docs/source/local-state/managing-state-with-field-policies.mdx index 04ad5f2a798..d796051b0e0 100644 --- a/docs/source/local-state/managing-state-with-field-policies.mdx +++ b/docs/source/local-state/managing-state-with-field-policies.mdx @@ -372,7 +372,7 @@ Note that even if you _do_ store local data as fields in the Apollo Client cache By default, neither a reactive variable nor the `InMemoryCache` persists its state across sessions (for example, if a user refreshes their browser). To persist this state, you need to add logic to do so. -The `apollo-3-cache-persist` library helps you persist and rehydrate the Apollo Client cache between sessions. For details, see [Persisting the cache](../caching/advanced-topics/#persisting-the-cache). +The `apollo3-cache-persist` library helps you persist and rehydrate the Apollo Client cache between sessions. For details, see [Persisting the cache](../caching/advanced-topics/#persisting-the-cache). There is currently no built-in API for persisting reactive variables, but you can write variable values to `localStorage` (or another store) whenever they're modified, and initialize those variables with their stored value (if any) on app load.