RealDevSquad / RealDevSquad/website-backend
Enhance Idle Members API
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
- In the following API, first we are getting only the members and then fetching the members having active tasks but do we also need to check if the user status is
ACTIVEorIDLEorOOO - Also, we are sending only the usernames from the backend but in frontend, for availability panel, we need user image to be shown from the user data and also for Tasks level feature we need users existing data so, it's if we send complete data of user instead of only usernames
https://github.com/Real-Dev-Squad/website-backend/blob/27ff92b7fdb37af413d93167b332ed3bd56800aa/controllers/members.js#L36-L51
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
The API logic is in controllers/members.js at lines 36-51; start by reading that flow and its current member/task filtering. Confirm the expected handling of ACTIVE, IDLE, and OOO users and the user fields needed by the availability panel and task-level feature, then verify the endpoint returns the agreed complete user data instead of usernames.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100