New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrap error response with Boom #158
Conversation
Sorry, but this is a terrible implementation of the feature. There are existing use-cases that requires information from the payload on status code errors, which is now impossible to retrieve. Further, all the helper methods don't even provide a way to access any headers on these errors. As it is, something like |
@kanongil I agree, would Boom.wrap not be better for this? |
@kanongil and @AdriVanHoudt you have access to the full response object, which is passed as the second argument in the callback. Additionally, the I am open to a better solution if either of you want to submit a PR. |
Full access, yes – but it has been aborted. Which means I won't be able to get the payload. |
As far as I can tell, this feature can only ever work for the helper methods, and the response behavior needs to be reverted. |
|
My PR would just be a revert of this commit. Then you can always create new option for this, as suggested in #82. |
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions. |
Fixes #82