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
Due to the handling of the tabulator ref, if the data prop is updated it leads to re-instantiating the Tabulator instance on the same DOM element without cleaning up the previous ref with .destroy(). See here: https://github.com/ngduc/react-tabulator/blob/master/src/ReactTabulator.tsx#L75. The ref is only cleaned up in the "unmount" useEffect, but it is re-used on subsequent calls to initTabulator.
This leads to a console warning on any events:
This can be reproduced on the codesandbox linked in the repo by triggering the "Asynchronous data" Set Data button then triggering a mouse event by double clicking a row in the table.
The text was updated successfully, but these errors were encountered:
Due to the handling of the tabulator ref, if the data prop is updated it leads to re-instantiating the Tabulator instance on the same DOM element without cleaning up the previous ref with
.destroy()
. See here: https://github.com/ngduc/react-tabulator/blob/master/src/ReactTabulator.tsx#L75. The ref is only cleaned up in the "unmount" useEffect, but it is re-used on subsequent calls toinitTabulator
.This leads to a console warning on any events:
This can be reproduced on the codesandbox linked in the repo by triggering the "Asynchronous data" Set Data button then triggering a mouse event by double clicking a row in the table.
The text was updated successfully, but these errors were encountered: