-
Notifications
You must be signed in to change notification settings - Fork 535
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
New web client expectation, result type differ from error type #2624
Comments
cc @vietj |
thanks I'll have a look |
I see the behaviour is different for this case, I am thinking that the decoding of the body should be applied only when responses are 2xx that would fix this issue |
The body may contain useful information (e.g. problem ID) in case of an error response. How can we get it? |
more thoughts about this: since Instead the webClient
.get("/test")
.expecting(expectation)
.map(response -> response.bodyAsJson(Integer.class)); Therefore we might have to deprecate the the |
Switching to new web client expectation ( #2607 ) occurre bug when body codec response is set.
Response is decoded prior to check expecting and result to a DecodedException
Version
Vertx 4.5.8
Do you have a reproducer?
same with JsonObject vs JsonArray, etc ..
The text was updated successfully, but these errors were encountered: