isFetchingNextPage is not always true in the next render cycle after fetchNextPage is called about query HOT 5 CLOSED

interesting. so I added another log that just imperatively reads queryClient.isFetching() right before calling fetchNextPage, and we can really see that it's already at 1 (which means there is a fetch going on) while the fetchNextPage variable is still at false:

 invoking fetchNextPage(), isFetching is 0
  fetchBranches()
 isFetchingNextPage: ❌
 invoking fetchNextPage(), isFetching is 1
  fetchBranches()
4 isFetchingNextPage: ✅
2 fetched 200 - 300

This could be because we batch updates to observers together to avoid frequent renders, but in this case, where every minimal scroll seems to trigger a re-render, this could interfer.

We allow overriding how we batch things in the latest v5 version with notifyManager.setScheduler

I tried setting it to not batch at all with:

notifyManager.setScheduler((cb) => cb());

and I haven't been able to reproduce the issue since.

You can also try requestAnimationFrame or queueMicrotask to see if that yields better results for you over our default settings.

from query.

Would it be possible to apply this setting to just one query

not possible, because it's about batching updates together, and that doesn't happen on a per-query level.

is it safe to use the requestAnimationFrame or queueMicrotask option for the entire project?

absolutely - any batching mechanism is okay. Some might result in more re-renders than others. We might switch default in a future major, but that's not decided.

from query.

I can't reproduce this in the sandbox and your video doesn't play for me ...

from query.

@TkDodo, try opening the video in a different browser. The example is reproducible, but it may require several attempts to see the issue.

from query.

Thanks, @TkDodo. Batching with setTimeout(callback, 0) as a default setting was the main reason why isFetchingNextPage wasn't updated in the next render cycle. cb = cb() works in 100% of cases 🎉, and requestAnimationFrame and queueMicrotask also work almost perfectly (I only saw one parallel request among 200 pages).

Would it be possible to apply this setting to just one query, not the entire project? If yes, how can it be done? If no, is it safe to use the requestAnimationFrame or queueMicrotask option for the entire project?

P.S. Also, it would be good to mention it here: TanStack Infinite Scroll

from query.