feat(notification): implement service #38
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This implements the
notificationservice in the backend. The following methods were implemented to be used through the message broker:sendTo: sends a notification to the specified user, this is non-blocking and is meant to be used without waiting for a replyfindAllOfUser: gets all the notifications of the specified seasonworker, corresponds to theGET /notificationsAPI routedeleteAllOfUser: deletes all the notifications of the specified seasonworker, corresponds to theDELETE /notificationsAPI routeOther changes
A new API route has been added,
DELETE /notifications, to clear all the notifications of the currently logged-in user.