From 6f9dcdf04c7d92b33ab8cc15b22e5b0d1b5c1abf Mon Sep 17 00:00:00 2001 From: Prazdevs Date: Mon, 2 Sep 2024 03:19:42 +0200 Subject: [PATCH] docs: update limitations hook name references --- docs/guide/limitations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guide/limitations.md b/docs/guide/limitations.md index b115c7e..aaf74a6 100644 --- a/docs/guide/limitations.md +++ b/docs/guide/limitations.md @@ -37,7 +37,7 @@ a === b // -> false As a consequence, reactivity between `a` and `b` is lost. :::tip Workaround -To get around this, you can exclude either `a` or `b` from being persisted (using the [`paths`](/guide/config#paths) option) and use the [`afterRestore`](/guide/config#afterhydrate) hook to re-populate them after hydration. That way `a` and `b` have the same refence again and reactivity is restored. +To get around this, you can exclude either `a` or `b` from being persisted (using the [`pick`](/guide/config#pick) option) and use the [`afterHydrate`](/guide/config#afterhydrate) hook to re-populate them after hydration. That way `a` and `b` have the same refence again and reactivity is restored. ::: ## Non-primitive types are not persisted @@ -46,6 +46,6 @@ Due to the serialization process, non-primitive types such as `Date` are not reh :::tip Workaround To get around this you can: -- Use the [`afterRestore`](/guide/config#afterhydrate) hook to recreate the objects after rehydration. +- Use the [`afterHydrate`](/guide/config#afterhydrate) hook to recreate the objects after rehydration. - Use a custom [`serializer`](/guide/config#serializer) that supports the data types you want to persist. :::