Skip to content
This repository was archived by the owner on Mar 13, 2018. It is now read-only.

Conversation

@x86ed
Copy link

@x86ed x86ed commented Feb 17, 2015

processError doesn't respond the same as processResponse. Errors aren't currently encoded whereas normal responses are, this changes the behavior so that the two behave in the same consistent way except process error now passes back a status object with the error code.

processError doesn't respond the same as processResponse. Errors aren't currently encoded whereas normal responses are, this changes the behavior so that the two behave in the same consistent way except process error now passes back a status object with the error code.
@googlebot
Copy link

Thanks for your pull request.

It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at https://cla.developers.google.com/.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check the information on your CLA or see this help article on setting the email on your git commits.

Once you've done that, please reply here to let us know. If you signed the CLA as a corporation, please let us know the company's name.

@x86ed
Copy link
Author

x86ed commented Mar 14, 2015

CLA signed. can someone please look at this?

@googlebot
Copy link

CLAs look good, thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants