Notifications are not synced to the state of the dappnode. #2323
Description
Describe the bug
Currently notifications are triggered when there's an update, or a condition for notification has been met (i.e.: proposed a block).
Some of these notifications are meant to signal that a potential change of state is ready - an update of a package, for example.
Nevertheless, when the state is changed (i.e.: the package is updated), the notification is not dismissed.
This is particularly annoying when autoupdates are activated, because the notification will trigger, the autoupdate will trigger shortly after, and by the time a user logs in, the state has changed / the package has updated, but the notification is still there.
Of course, the user cannot possibly know at first glance whether the state has changed or not - they only see a notification saying "The update is available", but maybe the update isn't available anymore because it has been updated. The user clicks on the notification and is directed to a page where it cannot take any action.
Moreover, the notification doesn't then disappear either, it has to be manually dismissed by pressing the X.
Expected behavior
- The notification should disappear when the state has changed.
- If the user needs to be informed that there has been an update, maybe a new notification saying: "This package has been auto-updated", but for sure 1. should happen - meaning the notification that the update is available should disappear instead.
- Package version:
- OS:
- Browser
Additional context
https://www.reddit.com/r/DAppNode/comments/1pc4is8/comment/nsrlbpn/?context=1