-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Chart stickiness - saved state #4379
Comments
I agree it'd be nice to save the state of the legend filters in the nvd3 charts specifically. |
I can take this. |
@betodealmeida thinking about this, maybe the slice object that's available in the visualization exposes a Another option would be to use individual |
@mistercrunch, I was planning to do this in 2-steps. I noticed that the ⚡ controls that trigger the render on change (with I thought of first fixing that first, and then make changes to the nvd3 legend so that is also updates the URL. This way the share button should be able to include the legend state, right? |
Yes lets fix the URL state getting out of sync. For the state to be saved in the slice it needs to make its way in the form data. As you know form data is a collection of control values. So either you add hidden controls or we add a new generic state key in form data. The url is built from the form form data of the slice. |
#4449 sets the foundation. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
Persist visualization settings during save.
Use case: User goes and plays around with chart, and gets to a point where they have enabled 2-3 series on the chart via clicking the legend. When they click save, the expectation is that the exact view that user has customized will be persisted, such that when they share this view, everything is intact.
Superset version
Expected results
Actual results
Steps to reproduce
The text was updated successfully, but these errors were encountered: