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
Because I have a lot of Data (>100'000 rows) I started implementing the infinite scrolling.
After Adding the Parameter maxPages
to the useInfiniteQuery, the data keeps loading but only the size * maxPages gets loaded and displayed. Not more. When you scroll up, the loading stops.
I think its not related to MRT and not to TanStack Query. The query does, what its should do
Can anybody please help?
Regards
Minimal, Reproducible Example - (Optional, but Recommended)
Do you intend to try to help solve this bug with your own PR?
No, because I do not know how
Terms
I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
The text was updated successfully, but these errors were encountered:
crypticbeing
added a commit
to crypticbeing/material-react-table
that referenced
this issue
Apr 23, 2024
material-react-table version
v2.13.0
react & react-dom versions
v18.2.0
Describe the bug and the steps to reproduce it
Hello
Because I have a lot of Data (>100'000 rows) I started implementing the infinite scrolling.
After Adding the Parameter
maxPages
to the useInfiniteQuery, the data keeps loading but only the size * maxPages gets loaded and displayed. Not more. When you scroll up, the loading stops.
I think its not related to MRT and not to TanStack Query. The query does, what its should do
Can anybody please help?
Regards
Minimal, Reproducible Example - (Optional, but Recommended)
open
material-react-table/apps/material-react-table-docs/examples/infinite-scrolling/sandbox/src/TS.tsx
Line 102 in 85b98f9
add new Line with the Parameter
maxPages: 4
run and scroll down in the table. When you reach 100 Fetches, the issue starts.
Screenshots or Videos (Optional)
Bildschirmaufzeichnung.vom.20.04.2024.00.12.41.webm
Do you intend to try to help solve this bug with your own PR?
No, because I do not know how
Terms
The text was updated successfully, but these errors were encountered: