Skip to content
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

12.0.0 Release Notes #165

Closed
geek opened this issue Mar 24, 2017 · 0 comments
Assignees
Milestone

Comments

@geek
Copy link
Member

@geek geek commented Mar 24, 2017

Summary

This release has a single change, which is breaking, related to the handling of error status codes in the request shortcut functions. The get, post, delete, and put functions now return a boom error with the headers and payload set as properties on the error object whenever the response status code is 400 or greater.

Breaking Change

PR #164 - The request function no longer wraps responses with an error status code using Boom, instead each of the shortcut functions (get, post, delete, and put) wraps the response in a Boom error object. Use error.isBoom to determine if you have a boom error and the properties on error.data to investigate the error cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.