RealDevSquad / RealDevSquad/website-backend
Cache the response /users/status api
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Description:
Currently '/users/status?state=IDLE' endpoint which returns the list of idle members does not have caching on our back-end.
Acceptance Criteria:
- Add the existing
cacheResponsemiddleware to '/users/status' endpoint to cache the response of the respective api. - Add
InvalidateCachemiddleware to all other API Endpoints which makes a change to user status.
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
Locate the /users/status route and the existing cacheResponse and InvalidateCache middleware, then identify every API endpoint that changes user status. Check how middleware is applied to nearby routes and run the relevant API tests or checks available in the repository. Done means the idle-member response is cached and every user-status change invalidates that cache.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100