Bad schema return type when created a generic wrapper class for response entity

[kamilkrzywanski]

project.zip
Bug Description
When I created a wrapper for ResponseEntity with a generic class inside, the API is generated with the wrapper type instead of the expected ResponseEntity type.

Steps to Reproduce

Create a custom wrapper for ResponseEntity with a generic class.
Generate API documentation (e.g., Swagger/OpenAPI).
Notice that the API uses the custom wrapper class instead of ResponseEntity.
Included a zip file with the code.

Expected Behavior
The API should return the exact type wrapped in the ResponseEntity, not the wrapper itself.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
The bug has already been fixed. I'll write tests and submit a PR shortly!

[bnasslahsen]

@kamilkrzywanski,

I have changed the fix, as it breaks other tests.
Do not hesitate to test the new latest SNAPSHOT.

[kamilkrzywanski]

You're right, I only checked my test and had hope that this project would have some pipeline.
I've reviewed your changes, and this approach works as long as we have only one wrapper. However, if we enclose it with another class, my test will fail again. I believe the issue mainly lies with ResponseEntity. My second mistake is that the excluded classes list contains interfaces, and we never get the exact class.

This approach pass all tests, and works in my opinion correct:
#2736