Skip to content

Too many components in swagger when using HttpEntity instead of ResponseEntity #280

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.

Sign up for GitHub

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

Jump to bottom
Closed
EstebanDugueperoux2 opened this issue Dec 18, 2019 · 3 comments
Closed

Too many components in swagger when using HttpEntity instead of ResponseEntity #280

EstebanDugueperoux2 opened this issue Dec 18, 2019 · 3 comments
Assignees
@EstebanDugueperoux2
Labels
enhancement New feature or request

Comments

@EstebanDugueperoux2
Copy link

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.
@springdoc
Copy link
Collaborator

springdoc commented Dec 18, 2019 •
edited
Loading

Hi,

The same behaviour of ResponseEntity will be applied to HttpEntity.

@code-d
Copy link

code-d commented Jan 17, 2020

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

62FED80E-BF24-458C-B6D5-E40B0BF7C5F9

@bnasslahsen
Copy link
Collaborator

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

@bnasslahsen bnasslahsen reopened this Jan 17, 2020
@bnasslahsen bnasslahsen added the enhancement New feature or request label Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EstebanDugueperoux2 EstebanDugueperoux2

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@code-d @bnasslahsen @EstebanDugueperoux2