RealDevSquad / RealDevSquad/website-backend
Desgin doc for task search by user improvement
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Issue Description
Design doc comparing and contrasting different approaches to improve task search by user
Expected Behavior
Design doc of -
- User filtering at client side
- User filtering at controller layer
- User filtering at model layer
- Migration of DB for better query control
Current Behavior
/userallows us to search user by querying
Reproducibility
- This issue is reproducible
- This issue is not reproducible
Severity/Priority
- Critical
- High
- Medium
- Low
Additional Information
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.
Research direction
The issue names the /user endpoint as the starting point; inspect its current user-search behavior and compare the client, controller, model, and database-migration approaches listed. Done means a design document that records the alternatives, trade-offs, and recommendation for improving task search by user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend, databases, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100