RealDevSquad / RealDevSquad/website-backend
Re-implement all PATCH APIs for user status
Open
@lakshayman is already working on this.
Since Feb 26, 2024.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.