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
Hi @rathboma I found that explicitly stating visibility on each column allows that data to persist. Not sure if it's supposed to persist without it being a part of the column config, so it could still be a bug in that sense.
This was happening because the persistence module was only tracking the values of keys that had actually been set in the column definitions.
As the documentation clearly states setting colums:true should include the visibility, i have just pushed a fix for this to the master branch and will include it in todays patch release.
It will now forcibly include the column visibility if columns is set to true.
@JacobGralinski as a helpful hint for you, if you need to set a value on every column, then rather than setting it manually on every column, you can use the columnsDefaults option in the constructor, any value in this object will be applied to all columns:
Tabulator persistence mode is not saving column visibility:
Steps to reproduce:
expected:
actual:
Config used:
The text was updated successfully, but these errors were encountered: