It seems unnecessarily restrictive to me to completely prevent access to the underlying Response when using the ResponseWrapper. Response has a lot of useful methods that ResponseWrapper doesn't replicate; getting a Response that allows you to use methods such as isRedirect() and isSuccessful() basically requires bypassing the request builder completely, at which point you might as well use the client directly.
I think it would be good to add a getResponse() method to ResponseWrapper that allows access to the Response object when necessary.
It seems unnecessarily restrictive to me to completely prevent access to the underlying
Response
when using theResponseWrapper
.Response
has a lot of useful methods thatResponseWrapper
doesn't replicate; getting a Response that allows you to use methods such asisRedirect()
andisSuccessful()
basically requires bypassing the request builder completely, at which point you might as well use the client directly.I think it would be good to add a
getResponse()
method toResponseWrapper
that allows access to theResponse
object when necessary.