-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1741 group multiple delete create notification requests into a single request #1744
base: dev
Are you sure you want to change the base?
1741 group multiple delete create notification requests into a single request #1744
Conversation
…f the dedicated endpoint in appserver.
return this.appServerService.addNotificationsBundle(notifications, subjectId, projectId) | ||
.then((resultNotification: FcmNotificationDto) => { | ||
this.setLastNotificationUpdate(Date.now()) | ||
// notification.notification.id = resultNotification.id |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to still store back the notification id? We would still need it when we want to cancel reminders/future notifications for a task once it has been completed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be done bij uncommenting the lines below right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No cause I think the request would return multiple notifications and each would be needed to get stored back to the task object.
As discussed RADAR-base/RADAR-Appserver#438 we reduce the number of requests by the aRMT application by multiple grouping create and delete notifications in one request.
fixes #1741