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.
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.