Building the Backend for handling the report feature - VERY IMP
- Dominant language
- TypeScript
- Stars
- 135
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
**Report Feature Backend Requirements**
_Socket Event Handler
Event name: "report"_
`{
reporterId: string (socket ID of the person submitting the report),
reportedId: string (socket ID or peer ID of the reported user),
roomId: string (the room/call ID where the incident occurred),
reason: string | undefined (optional reason for the report)
}`
### This is the frontend code which shows what things we are sending to the backend
What the backend should do:
-**Listen** for the "report" event from clients
-**Validate the data**: Ensure reporterId exists and is valid ,Ensure reportedId exists and is valid,Verify roomId exists ,Check if both users were actually in that room at the time
-**Store the report in your database with**:
Reporter's ID
Reported user's ID
Room ID
Reason (if provided)
Timestamp
Any additional context (IP addresses, session data, etc.)
Send acknowledgment back to the reporter (though the frontend already shows a toast)
Log the report for moderation review
you can pickup individual things to implement from this as well and get assigned from the mods
Contributor guide
Assessment
This issue has not been assessed yet.