Each of the controllers were implementing their delete functionality using deleteById. This method does not result in a broadcast to the front end. By replacing each of those method calls with the delete method, the broadcast occurs and the lists in the UI are update on delete.
Fixes #457
Type of change
Please delete options that are not relevant.
[X] Bug fix (non-breaking change which fixes an issue)
How Has This Been Tested?
[X] Manual Locally Testing
[X] Local Automated Testing
[ ] Manual Dev Testing
Checklist:
[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] Any dependent changes have been merged and published in downstream modules
Coverage remained the same at 45.273% when pulling ec89ddf899e88669d9dca151ac4670aad9b27ac7 on 457-delete-list-update into acc65c21bf73fc20ac4ead5f8a701476160732f0 on techdebt-staging.
Description
Each of the controllers were implementing their delete functionality using
deleteById
. This method does not result in a broadcast to the front end. By replacing each of those method calls with thedelete
method, the broadcast occurs and the lists in the UI are update on delete.Fixes #457
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Checklist: