RealDevSquad / RealDevSquad/website-backend
Refactor /taskRequests to suitable name following best api naming practices
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Description:
Currently the api name of taskRequests does not follow the good naming practices. This can be changed to either /task-requests or /tasks/requests/
After the change in backend API's the same should be updated in following UI repos:
To Do:
- Update the API in status site task details page.
- Update the API in dashboard task requests listing page.
- Update the API in dashboard task requests details page.
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 backend route currently exposed as /taskRequests and review the naming alternatives in the issue. Then trace its consumers in the status site task details page and the dashboard task requests listing and details pages. Done means the selected endpoint name and all three UI integrations are updated consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend-api-design, frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100