Too many components in swagger when using HttpEntity instead of ResponseEntity

[EstebanDugueperoux2]

Hello,

When having a resource method whose return type is HttpEntity instead of ResponseEntity, generated swagger contains too many technical types.
Reproductible in your unit tests by replacing ResponseEntity by HttpEntity.

Best Regards.

Hi,

The same behaviour of ResponseEntity will be applied to HttpEntity.

[code-d]

Hi,
the bug remains in webflux project
eg. when using Mono<HttpEntity<T>>or Flux<HttpEntity<T>>

[bnasslahsen]

It was only Handled for HttpEntity, return type
It will be Handled for Mono/Flux, in thé next release.