From bf7e0b858d6ad5198101ada67620967e0c5eaef6 Mon Sep 17 00:00:00 2001 From: Anthony Fertil Date: Wed, 15 Dec 2021 12:08:19 +0100 Subject: [PATCH 1/3] Update migrating-to-react-query-4.md Fix a typo in the migration guide --- docs/src/pages/guides/migrating-to-react-query-4.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/pages/guides/migrating-to-react-query-4.md b/docs/src/pages/guides/migrating-to-react-query-4.md index 630d4b225f..2bc7ec6c03 100644 --- a/docs/src/pages/guides/migrating-to-react-query-4.md +++ b/docs/src/pages/guides/migrating-to-react-query-4.md @@ -45,9 +45,9 @@ The `cancelRefetch` can be passed to all functions that imperatively fetch a que - `queryClient.invalidateQueries` - `queryClient.resetQueries` - `refetch` returned from `useQuery` -- `fetchNetPage` and `fetchPreviousPage` returned from `useInfiniteQuery` +- `fetchNextPage` and `fetchPreviousPage` returned from `useInfiniteQuery` -Except for `fetchNetxPage` and `fetchPreviousPage`, this flag was defaulting to `false`, which was inconsistent and potentially troublesome: Calling `refetchQueries` or `invalidateQueries` after a mutation might not yield the latest result if a previous slow fetch was already ongoing, because this refetch would have been skipped. +Except for `fetchNextPage` and `fetchPreviousPage`, this flag was defaulting to `false`, which was inconsistent and potentially troublesome: Calling `refetchQueries` or `invalidateQueries` after a mutation might not yield the latest result if a previous slow fetch was already ongoing, because this refetch would have been skipped. We believe that if a query is actively refetched by some code you write, it should, per default, re-start the fetch. From 6937cbc7bba395a82c7844a3388e74bccf0f2a36 Mon Sep 17 00:00:00 2001 From: Dominik Dorfmeister Date: Wed, 15 Dec 2021 12:09:48 +0100 Subject: [PATCH 2/3] Update docs/src/pages/guides/migrating-to-react-query-4.md --- docs/src/pages/guides/migrating-to-react-query-4.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/pages/guides/migrating-to-react-query-4.md b/docs/src/pages/guides/migrating-to-react-query-4.md index 2bc7ec6c03..72b0c4dd9d 100644 --- a/docs/src/pages/guides/migrating-to-react-query-4.md +++ b/docs/src/pages/guides/migrating-to-react-query-4.md @@ -42,8 +42,8 @@ In v4, `notifyOnChangeProps` defaults to the `"tracked"` behavior of v3 instead The `cancelRefetch` can be passed to all functions that imperatively fetch a query, namely: - `queryClient.refetchQueries` - - `queryClient.invalidateQueries` - - `queryClient.resetQueries` +- `queryClient.invalidateQueries` +- `queryClient.resetQueries` - `refetch` returned from `useQuery` - `fetchNextPage` and `fetchPreviousPage` returned from `useInfiniteQuery` From 6f9d60e45dc263ba8aed90f9ad907a01d1c42be3 Mon Sep 17 00:00:00 2001 From: Dominik Dorfmeister Date: Wed, 15 Dec 2021 12:13:00 +0100 Subject: [PATCH 3/3] Update docs/src/pages/guides/migrating-to-react-query-4.md --- docs/src/pages/guides/migrating-to-react-query-4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/pages/guides/migrating-to-react-query-4.md b/docs/src/pages/guides/migrating-to-react-query-4.md index 72b0c4dd9d..6d1535a19e 100644 --- a/docs/src/pages/guides/migrating-to-react-query-4.md +++ b/docs/src/pages/guides/migrating-to-react-query-4.md @@ -39,7 +39,7 @@ In v4, `notifyOnChangeProps` defaults to the `"tracked"` behavior of v3 instead ### Consistent behavior for `cancelRefetch` -The `cancelRefetch` can be passed to all functions that imperatively fetch a query, namely: +The `cancelRefetch` option can be passed to all functions that imperatively fetch a query, namely: - `queryClient.refetchQueries` - `queryClient.invalidateQueries`