SrigadaAkshayKumar/chatapp-frontend

Add Message Deletion Feature (Both Sides)

Open

#7 opened on Feb 9, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (3 forks)auto 404
Backendenhancementhelp wanted

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

🛑 Add Message Deletion Feature (Both Sides)

📌 Description

Currently, users can only delete messages from their own view, but the recipient still sees them. This feature will allow users to delete messages for both sender and recipient, enhancing privacy and control over conversations.

🚀 Feature Requirements

  • ✅ Add a "Delete for Me" option (removes message only for the user).
  • ✅ Add a "Delete for Everyone" option (removes message from both sender and recipient's chat).
  • ✅ Ensure a confirmation dialog before deletion.
  • ✅ Replace deleted messages with a placeholder like "This message was deleted."
  • ✅ Set a time limit (e.g., messages can only be deleted within X minutes after sending).

🛠 Tech Stack

  • Frontend: JavaScript / React
  • Backend: Firebase / Node.js

🔄 Possible Implementation Steps

  1. Update the message database schema to support soft deletion.
  2. Implement delete options in the chat UI.
  3. Ensure real-time updates so deleted messages disappear instantly.
  4. Test for edge cases, such as deleting a message while the recipient is online.

🏷 Labels

🔹 enhancement
🔹 help wanted

Contributor guide

Research direction
Study the current message model and Firebase schema. Design a soft deletion approach with a 'deleted' flag. Implement UI options with confirmation dialogs and set a time limit using server timestamps. Update real time listeners to hide deleted messages.
Tech stack
javascriptreactnodejsfirebase
Domain
full stack
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptReactNode.jsFirebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55