Feat: Allow Users to Edit and Delete Their Own Comments in shifting a…

[anshux1]

Proposed Changes

• Fixes Feat: Allow Users to Edit and Delete Their Own Comments in shifting and Resource #8701
• Added users to update their comments, with changes saved upon submission.
• Allowing users to remove their comments after confirming the action.

Screencast.from.2024-10-06.01-16-46.webm

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

• Add specs that demonstrate bug / test a new feature.
• Update product documentation.
• Ensure that UI text is kept in I18n files.
• Prep screenshot or demo video for changelog entry, and attach it to issue.
• Request for Peer Reviews
• Completion of QA

[netlify]

✅ Deploy Preview for care-ohc ready!

Name	Link
🔨 Latest commit	c8aebd5
🔍 Latest deploy log	https://app.netlify.com/sites/care-ohc/deploys/6701991cf7187300083d50be
😎 Deploy Preview	https://deploy-preview-8724--care-ohc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[bodhish]

@anshux1 does out backend even support this 🤔

In healthcare, we just don't allow users to delete data from the system. They can always add another a comment explaning the error.

[anshux1]

@bodhish I understand the sensitivity of data in healthcare systems.

Given this context, I propose the following approach:

1. For the edit functionality:

   • I'll open an issue in the backend repo to add a route for updating comments.
   • Once that's implemented, we can add the edit feature to the frontend.

2. For the delete functionality:

   • Instead of deleting comments, we could implement a "soft delete" where comments are marked as retracted but still visible in the system.

This approach maintains data integrity while still giving users some control over their comments.
Should i proceed with implementing the edit functionality and a modified version of the delete functionality?