Manual Pagination doesnt reset PageIndex when Manual Column Filtering. (server-side, v8)

[NathanGostelowGlobal]

Describe the bug

We have recently moved to use v8 of react-table and have noticed a bug where the pageIndex doesn't reset when we are using manualPagination and manualFiltering. This is when we are making server-side calls to get our data with the information.

In v7 it was the case that we would have our pageIndex reset to 0 when we make a filter change when we had both manualPagination && manualFiltering.

This resulted in the correct Query being made, however with the regression in behaviour in v8 we are seeing incorrect requests.

Your minimal, reproducible example

https://codesandbox.io/p/sandbox/festive-hertz-chekxf

Steps to reproduce

1. go to page 1000
2. filter on status complicated
3. you'll see page 1000/331 - with no data

Expected behavior

As a User when i am on a page I should be reset back to the first page when i filter and expect to see the the contents of the filter on page 1/331

How often does this bug happen?

Every time

Screenshots or Videos

Platform

• MacOS 13.2.1
• Chrome 111.0.5563.146

react-table version

V8.8.5

TypeScript version

No response

Additional context

No response

Terms & Code of Conduct

• I agree to follow this project's Code of Conduct
• I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

[talatkuyuk]

Have you tried autoResetPageIndex: false or autoResetPageIndex: true for your use case ?

[NathanGostelowGlobal]

Hi @talatkuyuk,

Adding autoResetPageIndex: true resets the pageIndex every time we navigate to a new page.

adding autoResetPageIndex: false never resets the pageIndex even when filtering.

unfortunately neither of these offer a solution to the underlying issue.

[talatkuyuk]

Got it. Your problem is not related with a bug in the react-table, related with mis-using the manual pagination.

If you follow manual pagination and manual filtering from server side, your API has to respond every time with the pagination data. I mean that whenever you make a new query with new filter parameters, your API has to contain new pagination data (if you don't request specific page from the server, it normally sends the first page of the filtered results having {pagination: {pageIndex: 0}} for example), so that you can apply this pagination data into table manually (by setting the pagination state of the react table according to API response). This is the manual pagination.

If you receive 1000 records and show 50 records in the page, this is not manual pagination.

If your API response does not contain the pagination data properly, you can fix your problem by manually resetting the pagination state of the table (pageIndex to 0) in a useEffect whenever receive a new filtered query result.

[NathanGostelowGlobal]

Hi Talatkuyuk,

Thanks for the reply!

The confusion here is that this change in behavior is a regression from the functionality of v7.

Is there any plan to support this old functionality in the future?