Calls `loadMore` endlessly
See original GitHub issueWhy would the component call loadMore
continuously and endlessly with increasing page numbers once I reach (only once) the end of the list? What am I doing wrong? FYI, I am using redux for this.
Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:10
Top Results From Across the Web
Android RecyclerView Load More, Endless Scrolling
It gives me an error saying “cannot call this method in a scroll callback” but it is fixed by calling recyclerView.post() method. Just...
Read more >How to implement endless list with RecyclerView?
Sometimes my loadMore() method called thrice in onScrolled(), Any idea why it is called thrice and how to stop calling it multiple times....
Read more >Endless Scrolling with AdapterViews and RecyclerView
Overview. A common application feature is to load automatically more items as the user scrolls through the items (aka infinite scroll).
Read more >loadMore function get called infinitely #163
I use React-Redux to pass loadMore and hasMore Code: import * as React from 'react'; ... I also get endless requests, solved it...
Read more >Infinite Scrolling with Android Paging Library and Flow API
What is endless scrolling? ... So our first line sets the page number we are at, and we called it “position”, if the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It has to do with my loading variable in the state being updated, If I remove “loading” from the state all is working fine. It seems when loading is done, it re-renders and thus calls the fetchMore function again.
Still doesn’t solve it but I’ll look into why a loading variable can cause the re-render…
The same happens to me but instead of reaching the end, it happens on page load, probably can be due to the fact that the component is not visible yet?