You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Method names for typescript are not generated according to the annotations and their method names when more than one method uses the same path prefix. The example will make it clear, i.e. to generate a method name favPartialUpdate is will generate patchModel. The example will make it clear.
To Reproduce
Steps to reproduce the behavior:
Define two routes with the same prefix but different last path section, in my case:
Expected behavior
That the method should be favPartialUpdate and not patchChannels
Screenshots
If applicable, add screenshots to help explain your problem.
Your swag version
swag version v1.16.3
Your go version
go version go1.22.4 linux/amd64
Desktop (please complete the following information):
Ubuntu 22.04
Additional context
I fixed the issue with following templates. But I cannot really remember what I changed, because it's month ago.
As far as I remember I changed the section of the code that analyses the route and generates the proper method name.
Describe the bug
Method names for typescript are not generated according to the annotations and their method names when more than one method uses the same path prefix. The example will make it clear, i.e. to generate a method name
favPartialUpdate
is will generatepatchModel
. The example will make it clear.To Reproduce
Steps to reproduce the behavior:
Expected behavior
That the method should be
favPartialUpdate
and notpatchChannels
Screenshots
If applicable, add screenshots to help explain your problem.
Your swag version
swag version v1.16.3
Your go version
go version go1.22.4 linux/amd64
Desktop (please complete the following information):
Additional context
I fixed the issue with following templates. But I cannot really remember what I changed, because it's month ago.
As far as I remember I changed the section of the code that analyses the route and generates the proper method name.
templates.zip
The text was updated successfully, but these errors were encountered: