You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! Thanks for maintaining this awesome library. It's been very productive for our team.
I stumbled on something while using it. When requests are made using the connector client (here, for example), the library is only checking whether the response is a 2xx status code and returning a custom error if not. There's some Microsoft documentation that indicates the presence of an ErrorResponse object in the response body and it would be nice to have that for debugging purposes.
It would be pretty easy to integrate into the HtErr field of theHTTPError type. I'm happy to submit a pull request for this.
The text was updated successfully, but these errors were encountered:
Hello! Thanks for maintaining this awesome library. It's been very productive for our team.
I stumbled on something while using it. When requests are made using the connector client (here, for example), the library is only checking whether the response is a 2xx status code and returning a custom error if not. There's some Microsoft documentation that indicates the presence of an
ErrorResponse
object in the response body and it would be nice to have that for debugging purposes.It would be pretty easy to integrate into the
HtErr
field of theHTTPError
type. I'm happy to submit a pull request for this.The text was updated successfully, but these errors were encountered: