RealDevSquad / RealDevSquad/website-backend
Update 'createTask' Middleware to Exclude 'COMPLETED' Status
Open
@shubhamsinghbundela is already working on this.
Since Oct 29, 2023.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Update 'createTask' Middleware to Exclude 'COMPLETED' Status
Overview:
The current system has a 'createTask' middleware that processes POST requests made to the '/task' endpoint. This middleware uses a constant object named 'TASK_STATUS' to determine the status of newly created tasks. However, there is an issue where the 'COMPLETED' status is erroneously included in the 'TASK_STATUS' object. This ticket aims to update the 'createTask' middleware to exclude the 'COMPLETED' status from the 'TASK_STATUS' object.
User Stories:
- As a super_user, I cannot pass status COMPLETED while creating a task
Acceptance Criteria:
- TDD
- The 'createTask' middleware should be modified to no longer include the 'COMPLETED' status in the 'TASK_STATUS' object.
- The 'createTask' middleware must still correctly handle all other aspects of task creation and status assignment.
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.
Assessment
This issue has not been assessed yet.