Prevent people from deleting datasources that have associate slices #3163
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've had people deleting datasources without knowing that other slices/dashboard were making use of them, breaking things. This should prevent that from happening.
This PR is also breaking down
superset/connectors/base.py
into a folder that aligns better with the relatedsqla
anddruid
folders.Ideally FAB would have something like the Django admin where it cascades deletes, but prompts the user first showing the tree of related objects getting deleted.