Describe the bug
Elsewhere, I've proven that the present codebase with Q-Table does not paginate; it is simply restricted to the default limit of hits allowed, and when those are painted, Q-Table does not raise the opportunity to paint more with a Next Button.
There are options, such as:
You pass in $skip: N which would allow an offset on each pass, but even that needs to be proven. So, the decision to simply make a fresh Pagination issue and start in again.
To Reproduce
Well described elsewhere
Expected behavior
When you hit the limit of the "window size" and there are more to see, a Next Button should show. When you are at the bottom window and you start scrolling up and hit the window size limit, a Previous Button should show.
Describe the bug Elsewhere, I've proven that the present codebase with Q-Table does not paginate; it is simply restricted to the default limit of hits allowed, and when those are painted, Q-Table does not raise the opportunity to paint more with a Next Button.
There are options, such as: You pass in $skip: N which would allow an offset on each pass, but even that needs to be proven. So, the decision to simply make a fresh Pagination issue and start in again.
To Reproduce Well described elsewhere
Expected behavior When you hit the limit of the "window size" and there are more to see, a Next Button should show. When you are at the bottom window and you start scrolling up and hit the window size limit, a Previous Button should show.
Additional context Some options:
Completely rethink how we fill Q-Table
Use a different Vue-based Table widget
Explore server-size pagination