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
Describe the bug
As documented in the comments in this PR, #2627, It seems like the original cancel flow for visualization plugin is quite confusing and unnecessarily complicated:
When user create viz from visualization page, no cancel button is shown
When user edit viz from visualization page, no cancel button is shown
When user tries to create viz from dashboard page, cancel button is shown
When user create viz from dashboard with add to dashboard after saving toggle off, then click save. It will direct back to the vis editor page, cancel button is not shown
When user edit viz from dashboard page, cancel button is shown
When user edit viz from dashboard page, made some changes, click save as. Toggle save as new visualization on, and add to dashboard after saving off, cancel button is not shown
When user edit viz from dashboard page, made some changes, click save as. Toggle save as new visualization off, and add to dashboard after saving off, cancel button is shown
I think we should rework and simplify the cancel flow for the visualization plugin so we could have a unified cancel flow throughout the app, ex. vis builder plugin.
One cancel flow can be:
cancel button will not be shown when user creates or edits vis builder from visualization page
cancel button will always be shown when user creates or edits vis builder from the dashboard page.
The text was updated successfully, but these errors were encountered:
Describe the bug
As documented in the comments in this PR, #2627, It seems like the original cancel flow for visualization plugin is quite confusing and unnecessarily complicated:
I think we should rework and simplify the cancel flow for the visualization plugin so we could have a unified cancel flow throughout the app, ex. vis builder plugin.
One cancel flow can be:
The text was updated successfully, but these errors were encountered: