Use drag-drop row with pagination

[enes-get-local]

I need to use row drag-drop and pagination together. But when i add drag-drop props pagination don't work.
There is any way to use both of these ?

Example Here
https://stackblitz.com/edit/react-ts-uthr9y?file=index.tsx

React-table version : 7.6.3

[maolivieri]

I have the exact same question. Appreciate if anyone could help.

[enes-get-local]

I have the exact same question. Appreciate if anyone could help.

I've found a way to do that. My problem was pagination resetting all data when drag and drop any row. İf you share example demo i can help

[maolivieri]

I have the exact same question. Appreciate if anyone could help.

I've found a way to do that. My problem was pagination resetting all data when drag and drop any row. İf you share example demo i can help

Thanks,
I got it now.

[maolivieri]

If anyone else has this problem.. you can stop the table from resetting as shown below.

......useTable(
{
data: records,
columns,
getRowId,
initialState: { pageSize: defaultPageSize ? defaultPageSize : 5 },
autoResetPage: false,
},.......

[kanounfoued]

The problem was, when using the drag and drop (Dnd library) on the table rows, and setting some rows as checked.
the state of the selected rows will be reseted automatically, whenever the user drag a row and drop it.

What I did:

I just remove the (data object) from the dependencies of useMountedLayoutEffect hook.

[github-actions]

This issue is being marked as stale (no activity in the last 14 days)

[github-actions]

This issue has been detected as stale and automatically closed. It's very likely that your issue has remained here this long because it would require breaking changes to v7. React Table v8 is currently in alpha (soon beta!) and already contains bug fixes, performance improvements and architectural changes that likely address this issue.

• If your v7 issue has been previously labeled as requiring breaking changes, please try the new v8 alpha/beta releases
• If your v7 issue has not already been labeled as a breaking change, open a new issue.
• If this was a v8 issue and was closed by mistake, please reopen or leave a comment below.