Real-Dev-Squad/website-backend

Re-implement all PATCH APIs for user status

Opened this issue · 0 comments

Issue Description

We are re-implementing the way we store user status. So for that, we have to update the four PATCH APIs /users/status/self, /users/status/update, /users/status/batch and /users/status/:userId according to the design doc https://docs.google.com/document/d/11kQ9MZ6gNjQ1EW9eruWWi8JeAjkIFLrWJ3s7rYVLEqc/edit?usp=sharing.

Expected Behavior

Update the user status in the new collection.

Current Behavior

Updating the user status in an old collection without storing change events.

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Checklist

  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.