-
Notifications
You must be signed in to change notification settings - Fork 271
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
Support for gin RouterGroup #17
Comments
@easonlin404 i see the same issue when i'm trying to create a project group for the api's.Do you think you have a quick patch for this to get fixed? |
@lukepatrick @kgrvamsi Actually |
Not exactly cross-package. A modular app layout. "microservices" perhaps. |
@lukepatrick Can you help to create a sample repo to reproduce this issue? I will check it. |
Sure, let me put something together |
actually, here is a link to an opensource project that covers my issue |
I check this issue after swag issue done. |
Any updates on this? We use gin groups to version (add a version path parameter) our api, but we can only set one base path atm (we would need two). |
yeah, we also use groups. This is a biggie actually. |
gin-swagger has the example about multiple api endpoints |
Giving swaggo a spin. It appears not to pull annotation information from a RouterGroup.
e.g.
main:
'Project'
do a
swag init
, get aswagger.yaml
The text was updated successfully, but these errors were encountered: