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
Another solution would be to expose a property that takes the original array (and id accessor?) for determining how to run animations. This way the responsiveness could be optimized further, for example by disabling animation for pre-existing rows that appear in bottom after a row has been removed, or for changes that are caused by sorting/filtering.
<DataTablebodyRef={bodyRef}data={data}// .../>
I don't pretend to know what a good API implementation would look like, just trying to give a general idea of the issue.
The text was updated successfully, but these errors were encountered:
Paginated DataTable with AutoAnimate displays animation on all rows when changing pages.
Animations should apply only on changes in the underlying data array instead of the slice that DataTable uses for populating pages.
A simple solution would be to disable animations on page changes altogether or by a property.
Another solution would be to expose a property that takes the original array (and id accessor?) for determining how to run animations. This way the responsiveness could be optimized further, for example by disabling animation for pre-existing rows that appear in bottom after a row has been removed, or for changes that are caused by sorting/filtering.
I don't pretend to know what a good API implementation would look like, just trying to give a general idea of the issue.
The text was updated successfully, but these errors were encountered: