Should ITable extensions use `saveState` by default?

[mwouts]

I have an ITable component in a Dash app. The table is refreshed periodically. When the data changes the underlying datatable object gets destroyed and re-created, and it loses its state, e.g. the columns that were unselected with the colvis button re-appear.

I see that simply passing saveState = True to the component (through update_itable_outputs) solves that problem. Should I make saveState = True the default in the app components (they all do a destroy / recreate when the table changes) ? @AllanJard do you see a potential drawback of doing so ?

[AllanJard]

You are correct - destroying and then recreating a table will cause it to revert to it's initial state. State saving can help address that if you want to keep it in the same state. You might want to consider reducing the state save duration ( https://datatables.net/reference/option/stateDuration ), unless you want state saving for the end user.

Worth noting that if you are just changing the data in the table, use the clear() method followed by rows.add() rather than destroying the table. That should be reserved for cases where you are changing the columns / data points in the table.