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
HttpRequest allows to define a response payload deserialiser but doesn't have options to specify an error deserialiser. Any non 2xx status response triggers a HttpException and the error message is deserialised to String leaving clients to parse/deserialise back to an error entity
Problem:
try {
HttpResponse<CreatePayoutResponse> response = client.execute(request);
} catch (HttpException e) {
String error = e.getMessage();
//Client to parse the error string to understand fields
}
Possible Solution:
Clients are expected to either parse the string to understand the fields or deserialise the entity themselves like
General information
Issue description
HttpRequest allows to define a response payload deserialiser but doesn't have options to specify an error deserialiser. Any non 2xx status response triggers a HttpException and the error message is deserialised to String leaving clients to parse/deserialise back to an error entity
Problem:
Possible Solution:
Clients are expected to either parse the string to understand the fields or deserialise the entity themselves like
Expectation:
It would improve the integration experience to allow the error type be available in the HttpException
The text was updated successfully, but these errors were encountered: