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
VisBuilder Visualizations have internal state that they would like to persist when changed. Currently we do not persist this data.
Note: We may want to hold off on implementing this until the migration to vega-lite is complete. f we cant wait for that, we need to investigate the impact of the migration on the saved object data since the uistate after migration may be drastically different from that of the legacy library.
The text was updated successfully, but these errors were encountered:
@BSFishy, today a user can interact with a visualization that lets them set values in the visualization, e.g. The color for a line chart or the sort order for the table visualization. This value is not saved with the visualization and then the user reloads the visualization, this information is lost. The goal of this issue os to allow for those values to persist.
VisBuilder Visualizations have internal state that they would like to persist when changed. Currently we do not persist this data.
Note: We may want to hold off on implementing this until the migration to vega-lite is complete. f we cant wait for that, we need to investigate the impact of the migration on the saved object data since the uistate after migration may be drastically different from that of the legacy library.
The text was updated successfully, but these errors were encountered: