Still emit response if return type is Void #8367
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this patch, HttpClient would remove the actual response from the response publisher if the expected body type is Void. I don't see a reason to do this, and it leads to HTTP filters not seeing the response as they should.
However there is an outstanding bug that this uncovered: If there is a declarative client method that is supposed to return Publisher, it instead always returns a Publisher<HttpResponse> (the type returned from HttpClient.exchange). The code here does not convert properly when the
returnType
isPublisher<Void>
and the result is another publisher:micronaut-core/aop/src/main/java/io/micronaut/aop/internal/intercepted/PublisherInterceptedMethod.java
Lines 112 to 118 in f81ecea
HttpGetSpec.test simple get with Publisher<Void> return
.@dstepanov do you have any idea how to fix this?
Fixes #8366