fix: update fetchNextPage condition in Example component #9626
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the infinite scroll example, I added
hasNextPage && !isFetchingNextPage
guards to theuseEffect
that triggersfetchNextPage
.Without these guards, the effect may fire multiple times or after there are no more pages, causing unnecessary fetches.
This aligns the example with recommended usage from the docs of
useInfiniteQuery
.Summary by CodeRabbit
Bug Fixes
Performance