From d0e46f639dfc8f930cd25637c49b11190caeed1d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=BA=84=E5=AE=8F=E5=9F=BA?= Date: Fri, 1 Jul 2022 13:01:21 +0800 Subject: [PATCH] docs: fix the typo in persistQueryClient.md Update subtitle `PeristQueryClientProvider` to `PersistQueryClientProvider`. --- docs/plugins/persistQueryClient.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/plugins/persistQueryClient.md b/docs/plugins/persistQueryClient.md index 04b104e203..2b48c08790 100644 --- a/docs/plugins/persistQueryClient.md +++ b/docs/plugins/persistQueryClient.md @@ -175,7 +175,7 @@ persistQueryClient({ ReactDOM.createRoot(rootElement).render() ``` -### PeristQueryClientProvider +### PersistQueryClientProvider For this use-case, you can use the `PersistQueryClientProvider`. It will make sure to subscribe / unsubscribe correctly according to the React component lifecycle, and it will also make sure that queries will not start fetching while we are still restoring. Queries will still render though, they will just be put into `fetchingState: 'idle'` until data has been restored. Then, they will refetch unless the restored data is _fresh_ enough, and _initialData_ will also be respected. It can be used _instead of_ the normal [QueryClientProvider](../reference/QueryClientProvider):