fix: Make call to updateMetamaskNotificationsList
async and fix its event emission.
#4826
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.
Explanation
updateMetamaskNotificationsList
function is async and the registered message handler should also have been async. TheNotificationServicesController:notificationsListUpdated
event is not being received by the extension.updateMetamaskNotfiicationsList
function was never called in the extension until now (with snaps). When triggering a notification, with the current state of things, the extension would not update the badge counter because it wasn't receiving theNotificationServicesController:notificationsListUpdated
event.Changelog
@metamask/notification-services-controller
updateMetamaskNotificationsList
was fixed by updating the message handler and moving the publish call outside of the update to state in the function.Checklist