pillarjs / pillarjs/finalhandler
Respect `expose` on thrown errors
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 241
- Forks
- 54
- Avg merge
- 7h 21m
- Merged PRs (30d)
- 1
Description
https://www.npmjs.com/package/http-errors
When we're extracting the message out of a thrown error, we should consider respecting the expose property on it so that we provide consumers some way of exposing information to the client in the event that they want to return something like an HTTP 400 by using throw BadRequest('You must include an Id') from http-errors or a similar lib.
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
No file or test is named. Start by locating finalhandler's thrown-error message extraction path and compare it with the expose behavior described for http-errors. Done means the response respects an error's expose property while preserving the requested client-facing message for exposed errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100