[Backend] — Bulk Notification Read/Unread Endpoint

[Olowodarey]

Labels: backend, enhancement, notifications

Problem

Users must mark notifications read one at a time; there is no bulk or mark-all operation, causing many round-trips.

Requirements

1. Add endpoints to mark a list of notifications, or all, as read/unread.
2. Scope operations to the authenticated user.
3. Return the updated unread count.
4. Make the operation idempotent.

Acceptance Criteria

• Bulk and mark-all update only the caller's notifications.
• The response includes the updated unread count.
• Repeating the operation is idempotent.
• Tests cover bulk, mark-all, and scoping.

Files

backend/src/notifications/notifications.service.ts, backend/src/notifications/notifications.controller.ts, backend/src/notifications/dto

[odusanya03]

@odusanya03 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

​Hi maintainer, I would love to work on this issue. I can get started on it right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @odusanya03 to this issue.

[Victorjonah-prog]

@Victorjonah-prog has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Here's a short, simple application text:

Hi, I'd like to work on this issue. I have experience building backend endpoints in Node.js/NestJS-style architectures, including scoped, idempotent bulk operations. I understand the requirements: adding endpoints to mark a list of notifications (or all) as read/unread, scoped to the authenticated user, returning the updated unread count, and ensuring idempotency, with changes in notifications.service.ts, notifications.controller.ts, and the dto folder. I'll also add tests covering bulk updates, mark-all, and user scoping. Happy to get started right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Victorjonah-prog to this issue.

[iyanumajekodunmi756]

@iyanumajekodunmi756 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @iyanumajekodunmi756 to this issue.

[drips-wave]

Congratulations, @iyanumajekodunmi756! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @iyanumajekodunmi756: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @iyanumajekodunmi756 as part of the Stellar Wave Program's 7th Wave 🥳

😎 @iyanumajekodunmi756: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.