[BE-39] In-app messaging: backend

[yusuftomilola]

Overview

Members and admins have no direct communication channel within the platform. Members can only contact the hub via the public contact form which has no thread history. In-app messaging enables member-to-admin and member-to-member communication with full history.

Context

• NotificationsModule: backend/src/notifications/ — emit real-time event on new message
• WebSocket gateway (BE-01): backend/src/notifications/gateway/notifications.gateway.ts
• User entity: backend/src/users/entities/user.entity.ts

Tasks

• Create MessageThread entity: id, participantIds (JSON array of User IDs), lastMessageAt (timestamptz), createdAt
• Create Message entity: id, threadId (FK), senderUserId (FK), body (text), isRead (bool, default false), sentAt (timestamptz)
• POST /messages/threads — start a thread by specifying one or more participant user IDs (authenticated member or admin)
• GET /messages/threads — list the current user's threads, sorted by lastMessageAt desc, each including the last message preview
• GET /messages/threads/:id/messages — paginated message history for a thread (participants only)
• POST /messages/threads/:id/messages — send a message; updates lastMessageAt on the thread; emits a new-message WebSocket event to all participants
• PATCH /messages/threads/:id/read — mark all unread messages in the thread as read (for current user)
• GET /messages/unread-count — returns total unread message count for the current user (for badge display)

Files to Modify / Create

• New: backend/src/messaging/ (module, entities, controller, service, providers)
• backend/src/app.module.ts

[madisonsc52-del]

@madisonsc52-del has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer i can work on this, I'll make sure to work on the issue asap

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

[Olajcodes]

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

Hi maintainer! I would love to help you with this issue. Given my theoretical knowledge and background, I am quite sure that I am well-equipped to tackle it. Please kindly assign it to me.

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

[Uyoxy]

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

can i work on this

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

[grantfox-oss]

🦊 GrantFox — @Uyoxy has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1225)
2. Your PR will be reviewed by the DistinctCodes maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

🧑‍💻 @Uyoxy: 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 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Uyoxy's PR #1323 was approved and merged by @yusuftomilola.

🏆 @Uyoxy: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (433 total points). Track your full progress on GrantFox.

👏 Great work, @Uyoxy! Keep contributing to DistinctCodes.