Implement predictable error objects
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Currently error objects are lazily slapped with what are sometimes irrelevant HTTP `statusCode` properties. The errors returned should be application-specific, and differentiate the various scenarios that can be encountered.
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 where error objects are created and where HTTP statusCode is added, then trace the callers that handle those errors. Define the application-specific scenarios and predictable object shapes from the existing behavior; done means each scenario is distinguishable without irrelevant statusCode properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100