Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[VisBuilder] Persist visualization internal state #3124

Closed
ashwin-pc opened this issue Dec 22, 2022 · 2 comments · Fixed by #3751
Closed

[VisBuilder] Persist visualization internal state #3124

ashwin-pc opened this issue Dec 22, 2022 · 2 comments · Fixed by #3751
Assignees
Labels

Comments

@ashwin-pc
Copy link
Member

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.

@BSFishy
Copy link
Contributor

BSFishy commented Dec 29, 2022

@ashwin-pc Can we have more information about what you mean by "internal state"?

@ashwin-pc
Copy link
Member Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants