-
Notifications
You must be signed in to change notification settings - Fork 9
Support complex generic type response mapping procesing #150
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
Comments
According to swagger reference to openapi specification, the correct way to define Dictionary or Map is to specify SpringDoc annotation processing generates something like this for the
I've tried several definitions with no result and didn't find It might be better to add |
at the moment, only one level of generic is supported in the mapping (I think it is in the docs). I didn't spent any time yet to find out what it would take to support more levels. |
yes, there is no code that checks |
…erics of parameter
…erics of additional parameter
…erics of response
…ted generic parameter/response
… with generic types
…erics & nested generics
Hi @hauner!
Processing response mapping of generic types with depth 1 works fine:
But it doesn't work with a complex generic types such as:
FooToBar => java.util.Map<java.lang.String, java.lang.List<java.lang.String>>
The output of processing:
It would be useful to add complex generic types support.
The text was updated successfully, but these errors were encountered: