Source tab on Edit Dataset modal inconsistent with Datasource on Chart Explore view
See original GitHub issue~1week ago a change was merged redesigning the modal “Edit Datasource” on Chart Explore. It is not clear what should be the behavior of the section Source on Edit Dataset:
Context
Use case 1: Changing datasource using Change Datasource This change is local - only for the chart user has open. This works as expected.
Use case 2: Changing datasource using Edit Datasource --> Source Previously the Source tab was last on the right side, merged with settings. It’s unclear what is changing the source on this modal supposed to do. Typically, any changes to “Edit Datasource” are applied globally to ALL CHARTS using the datasource. User is warned about this. What is changing the source on the 1st tab actually supposed to do?
Current behavior:
Currently, if you change the name of table (Datasource) nothing happens.
After saving the change nothing happens to the chart, and the changes are not saved when opening the modal again.
Expected behavior:
Unclear. If this is another way to change datasource LOCALLY for the one chart, (1) the warning shouldn’t be displayed and (2) the change should apply to the current chart. This change should not apply globally to all charts.
How to reproduce the bug
- Go to Chart Explore
- Click on Edit Datasource
- On 1st tab (Source) change the name of table
- Save
- Nothing happens
Environment
- superset version:
master
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
- I have checked the superset logs for python stacktraces and included it here as text if there are any.
- I have reproduced the issue with at least the latest released version of superset.
- I have checked the issue tracker for the same issue and I haven’t found one similar.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (7 by maintainers)
Top GitHub Comments
I agree that this functionality is a bit redundant and if we keep it modal, the warning message should be either louder and more specific. Zuzana, let’s explore a better solution after getting the bug fix. Thanks for suggesting!
On Wed, Oct 14, 2020 at 9:39 AM zuzana-vej notifications@github.com wrote:
Closing this as we had some discussions and this bug is resolved. There is a new different bug - raising new issue for tracking.