Skip to content
This repository has been archived by the owner on Jun 20, 2022. It is now read-only.

Always return *ResponseError in NewReesponseError #56

Merged
merged 1 commit into from
Feb 23, 2014

Conversation

owenthereal
Copy link
Contributor

Previously it could happen that the response body can't be decoded and the
return error is a different type from *ResponseError. This causes downstream
usage to handle different types of errors.

The solution is to always return *ResponseError and make the decoding error as
part of the *ResponseError.

Previously it could happen that the response body can't be decoded and the return error is a different type from *ResponseError. This causes downstream usage to handle different types of errors.

The solution is to always return *ResponseError and make the decoding error as part of the *ResponseError.
@pengwynn
Copy link
Collaborator

👍

owenthereal added a commit that referenced this pull request Feb 23, 2014
Always return *ResponseError in NewReesponseError
@owenthereal owenthereal merged commit 24c866c into master Feb 23, 2014
@owenthereal owenthereal deleted the always_return_response_err branch February 23, 2014 21:33
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants