1 reply

Handling Text Responses and Accessing Raw Errors with `HttpApi`

With

HttpApi

HttpApi

(defining spec for a 3rd party API), is there any way to handle text response? Seems like

ParseError

ParseError

eats any potential to get access to the raw response and the error becomes inaccessible. Even if it was possible to get the

ResponseError

ResponseError

instead of

ParseError

ParseError

that would be great (basically

ParseError

ParseError

in these seems to be hiding everything)

Example raw response (mocked fetch function to get access to it)

status: 400,
body: 'Request body deserialize error: data did not match any variant of ...'

status: 400,
body: 'Request body deserialize error: data did not match any variant of ...'