Currently the logic mostly lives in the BackupTask model, which was okay when it was just a couple of notification choices but it's getting pretty unweildly.
In the future this should be addressed and extracted into its own set of classes in the app/Services directory.
Notifications are pretty well tested and that's not an area I'm concerned about, but it could do with some love to make it less messy to work on. There doesn't need to be any change in functionality but I am concerned about the code in the long-term.
Contact Details
No response
Refactoring Title
Improve notification stream
Refactoring Description
Currently the logic mostly lives in the BackupTask model, which was okay when it was just a couple of notification choices but it's getting pretty unweildly.
In the future this should be addressed and extracted into its own set of classes in the
app/Servicesdirectory.Notifications are pretty well tested and that's not an area I'm concerned about, but it could do with some love to make it less messy to work on. There doesn't need to be any change in functionality but I am concerned about the code in the long-term.
Current Issues
No response
Additional Context
No response