RealDevSquad / RealDevSquad/website-backend
Change the `status` key to `legacy_status` in `\users\:userName` endpoint
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Currently, in the \users\:userName endpoint we get the object which has a key status and its value is one of the items in this list [ ooo, active, idle]. We are also creating a new Status collection. Hence we need to change the status key in the \users\:userName endpoint to legacy_status. Also wherever in our apps we are using status it needs to be updated to legacy_status so that our Apps don't break because of this change.
TLDR:
- Change
statuskey tolegacy_statusin\users\:userNameendpoint. - Update the
statuskey tolegacy_statusin all the apps.
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.
Research direction
Start by locating the users/:userName endpoint and identify every app reference to the existing status key. Update the endpoint and all consuming apps consistently, then verify that no affected app still expects status and that the new legacy_status response works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100