RealDevSquad / RealDevSquad/website-backend
[RFC] Merge Task and Extension and fix naming convention of task and extension requests
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Description:
We currently have separate collections for extension & task requests. We can merge this into one and fix the route names.
Suggested route names : /task?type=extension-request or /task?type=task-request
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 current extension-request and task-request collections and their route definitions. Compare their existing behavior, then determine how both should be represented through /task?type=extension-request and /task?type=task-request; done means the collections are merged and the route names follow the proposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100