Fix for generic HTTP 404 errors
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 621
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
Not all 404 errors should return {"Message":"No task or report with that ID found!"}
Contributor guide
No contributing guide indexed for this repository
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 HTTP 404 handling in the Python application and trace how the response message is selected. Done means generic 404 errors no longer return the task/report-specific message, while the issue's stated behavior remains covered by tests if existing tests can be found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100