-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Nested Generic Fields #1304
Comments
@FabianMartin sorry to tag you again. Just thought that this could potentially be interesting for you to know about. Your merged code works beautifully out of the box, but not when the generic field declaration is in another package. The linked repo above should demonstrate the issue well. |
… another package - change full name generation and support SelectorExpr - prepend package only, if no name does not contain package fixes swaggo#1304
Thank you for the test repo. You find the fix in PR #1305 |
Much appreciated @FabianMartin, your contributions means a lot 🙏 |
Describe the bug
Nested Generic fields still not supported even after #1277 and #1281 on certain occasions.
To Reproduce
Have a look at the following repo https://github.com/chaintraced/swaggo-issue-repo
On the
main
branch you will see that it is not working as intended, whilst on the branch functional-branch it's working beautifully.The only difference being that the nested generic field is in another package on the main branch, very interesting behaviour.
Expected behaviour
I expect the generic field to be properly read and generated
Your swag version
I forked the repo to be able to release a version including the latest generic code changes
https://github.com/chaintraced/swag
Your go version
e.g. 1.18.0
The text was updated successfully, but these errors were encountered: