Closed myyrakle closed 6 months ago
Try the latest version of swag.
Since I use the latest version, there is no panic, but it doesn't generate like an array.
I think this is probably intentional behavior from here on out. We will custom process the rest ourselves.
The issue is closed.
Describe the bug To reduce boilerplate, I defined a generic array type instead of using a named type of array.
To Reproduce First of all, I defined the following generic array wrapper:
Previously, I defined and used the following response dto type.
But if I apply a generic type like this:
It panics and fails.
Expected behavior In my opinion, since generics are removed from preprocessing, they should behave the same as they would without generics. But it didn't work that way.
Of course, I know that the principle is different since this is generate before compilation. Is support for these features possible?
Screenshots![image](https://github.com/swaggo/swag/assets/16988115/01f5487c-ad75-41e0-8ec9-1c7e79547078)
Your swag version v1.8.6
Your go version go version go1.20.6 darwin/arm64
Desktop (please complete the following information):
Additional context