-
Notifications
You must be signed in to change notification settings - Fork 297
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
Option for not transforming error responses #131
Comments
Well, I have to admit that I am not aware of many different use cases for the Anyway, the change at least decoupled the implementation of the function passed to Considering the gained decoupling – which we should keep – I take your suggestion of the
What do you think? |
Yeah, that looks good. I'm using |
Hi @stevage , I just released |
Oh, nice one :) |
I realise I'm too late on this one, and just discovering request-promise now, but this (#86) seems like a really weird change. I'm using transform to extract part of the body of a successful API query. I can't really imagine ever wanting to apply the same function to both successful and unsuccessful queries.
Before:
After:
Seems like a lot of ugly boilerplate for nothing.
Perhaps an option,
transformErrors: false
, to restore the previous behaviour.The text was updated successfully, but these errors were encountered: