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
Is your feature request related to a problem? Please describe.
Currently, I have to manually define URI parameters in my Go code when using swag to generate documentation. This can be tedious and error-prone, especially when dealing with structs that have multiple fields.
Describe the solution you'd like
I would like swag to automatically extract URI parameters from struct tags. For example, if I have the following struct:
swag should recognize that Code is a URI parameter (based on the uri:"code" tag) and include it in the generated documentation accordingly. This would streamline the process of defining API endpoints and reduce the risk of errors.
Describe alternatives you've considered
I could continue to manually define URI parameters, but this is not ideal. I could also explore other documentation generators, but I prefer swag due to its ease of use and integration with Go.
Additional context
This feature would be particularly useful for APIs that have many endpoints with complex URI structures. It would also improve the consistency and accuracy of documentation.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, I have to manually define URI parameters in my Go code when using swag to generate documentation. This can be tedious and error-prone, especially when dealing with structs that have multiple fields.
Describe the solution you'd like
I would like swag to automatically extract URI parameters from struct tags. For example, if I have the following struct:
swag
should recognize thatCode
is a URI parameter (based on theuri:"code"
tag) and include it in the generated documentation accordingly. This would streamline the process of defining API endpoints and reduce the risk of errors.Describe alternatives you've considered
I could continue to manually define URI parameters, but this is not ideal. I could also explore other documentation generators, but I prefer swag due to its ease of use and integration with Go.
Additional context
This feature would be particularly useful for APIs that have many endpoints with complex URI structures. It would also improve the consistency and accuracy of documentation.
The text was updated successfully, but these errors were encountered: