When a database and their activities are deleted, calculation setups should reflect this by removing any affected functional units. This does already happen automatically (?) for removing individual flows. With this PR this also happens for database deletions by connecting the CS Controller to the delete_database_confirmed signal.
Closes #1238
Though without @marc-vdm 's information suggestions. I suggest adding them later after the controller rework.
Checklist
[x] Keep pull requests small so they can be easily reviewed.
[x] Categorize the PR by setting a good title and adding one of the labels:
bug, feature, ui, change, documentation, breaking, ci
as they show up in the changelog.
coverage: 50.611% (-0.04%) from 50.652%
when pulling 97d9af610734e8bdaf87a6b83f57c08e5328de9d on mrvisscher:fix-cs-update-on-db-delete
into ffa5ad8495fcf3743a0ffe5b56cc225dd0d6b7d6 on LCA-ActivityBrowser:master.
When a database and their activities are deleted, calculation setups should reflect this by removing any affected functional units. This does already happen automatically (?) for removing individual flows. With this PR this also happens for database deletions by connecting the CS Controller to the
delete_database_confirmed
signal.Checklist
bug
,feature
,ui
,change
,documentation
,breaking
,ci
as they show up in the changelog.