autoResetPageIndex not resetting properly

[marcellino-ornelas]

TanStack Table version

8.15.0

Framework/Library version

^18.2.0

Describe the bug

Hello, Im running into a issue with the autoResetPageIndex showing/processing the incorrect page Index when using client side pagination and changing the rows per page.

Steps to reproduce

1. Click next page 2 times so you see Page 3 of 10,000
2. Click the rows per page option
3. Select option show 20

You will now see the incorrect number Page 2 of 5,000

Expected behavior

1. Click next page 2 times so you see Page 3 of 10,000
2. Click the rows per page option
3. Select option show 20

You should now see Page 1 of 5,000

How often does this bug happen?

Every time

Platform

• macOS 14.4.1
• Chrome 123.0.6312.87 (Official Build) (x86_64)

TypeScript version

5.1.6

Your Minimal, Reproducible Example - (Sandbox Highly Recommended)

https://stackblitz.com/edit/tanstack-table-csasqf?file=src%2Fmain.tsx

Screenshots or Videos (Optional)

Screen.Recording.2024-04-01.at.4.44.46.PM.mov

Do you intend to try to help solve this bug with your own PR?

No, because I do not know how

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.

[marcellino-ornelas]

Current work around

const handleChangeRowsPerPage = useCallback(
        (event: React.ChangeEvent<HTMLInputElement>): void => {
            table.setPageIndex(0);
            table.setPageSize(Number(event.target.value));
        },
        [table],
    );

[KevinVandy]

In my initial testing, it appears to me that the table is going back to the correct initial page upon a sort, but not upon a pageSize change.

This is the expected behavior. Only events such as sorting, filtering, or grouping should trigger an auto-reset. Changing the page size should not trigger this. Your workaround is the solution if you want that behavior though.

There are edge case scenarios that are similar to this, but not exactly the same that are being considered to be fixed. #5031