fix: generic types name generation #2083
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the PR
During
swag initwhen usinguseStructNameflag. Fixed the issue where types using in generic were generated with full path instead of only type name.Relation issue
Expands changes introduced in #2043
Additional context
Assume following code example:
When generating swagger with
swag init --st --dir . --ot yaml --stThe resulting type definition in swagger looked something like:
We see that
APIResponseis generated correctly with only struct name, when type used in generic is generated with full path.After change the definion looks correct, with underling generic type shortened:
I know the tests are broken now. However, I cannot think of any better solution right, and help is welcomed and will be highly appreciated