You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// isIdle will be `true` until `enabled` is true and the query begins to fetch. It will then go to the `isLoading` stage and hopefully the `isSuccess` stage :)
556
+
// isIdle will be `true` until `enabled` is true and the query begins to fetch.
557
+
// It will then go to the `isLoading` stage and hopefully the `isSuccess` stage :)
557
558
```
558
559
559
560
## Caching & Invalidation
@@ -668,7 +669,7 @@ When using `useInfiniteQuery`, you'll notice a few things are different:
668
669
669
670
### Example
670
671
671
-
Let's assume we have an API that returns pages of `projects` 3 at a time based on a `cursor` index along with a cursor that can be used to fetch the next group of projects
672
+
Let's assume we have an API that returns pages of `projects` 3 at a time based on a `cursor` index along with a cursor that can be used to fetch the next group of projects:
672
673
673
674
```js
674
675
fetch('/api/projects?cursor=0')
@@ -769,7 +770,7 @@ function Projects() {
769
770
770
771
### What if I want to infinitely load more data in reverse?
771
772
772
-
Sometimes you may not want to **append**infintely loaded data, but instead **prepend** it. If this is case, you can use `fetchMore`'s `previous` option, eg.
773
+
Sometimes you may not want to **append**infinitely loaded data, but instead **prepend** it. If this is case, you can use `fetchMore`'s `previous` option, eg.
0 commit comments