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
When the column preferences are applied the column is updated directly,
but some preferences can only be applied if the column is of a specific
type (e.g. NumberColumn). If there are preferences set for these cases
the preferences are lost. Normally this is ok, because the column can
not handle these preferences, but it makes it impossible to e.g. use
placeholder columns if the real column can only be created
asynchronously. Therefore, introduce the interface
ColumnPreferencesColumn which contains a getter and a setter for the
whole preferences. If preferences are applied to such a column the whole
TableColumnClientUiPreferenceDo is passed to the setter and later on
these preferences are used as a fallback for preference values that can
only be extracted from specific column types when the preferences are
stored.
449721
if(options?.applyUserFilters){// true when showing a bookmark
517
529
table.applyUserFilterStates(userFilterStates);
518
530
}
519
531
}
532
+
533
+
isColumnPreferencesColumn<TValue>(column: Column<TValue>&Partial<Omit<ColumnPreferencesColumn<TValue>,keyofColumn<TValue>>>): column is ColumnPreferencesColumn<TValue>{
0 commit comments