RealDevSquad / RealDevSquad/website-backend
Fix bug in task update logic - computes isNewProgress0 incorrectly
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
controllers/tasks.js computes isNewProgress0 incorrectly because !!req.body.percentCompleted !== undefined is always true.
Replace with req.body.percentCompleted !== undefined.
File & line: controllers/tasks.js line 378
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
Open controllers/tasks.js and inspect the task update logic around line 378, focusing on how percentCompleted is checked. Confirm the condition distinguishes an undefined value from other values, then verify the update behavior for requests with and without percentCompleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100