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
I was running swag in my package -> vendor-service. But due to a vendor prefix check, all the files are being ignored and swagger docs are not generated.
To Reproduce
Steps to reproduce the behavior:
Create a package with starts with "vendor"
Add an API and swagger annotation to that API
Run swag init
Check docs/swagger.json does not have the swagger documentation data
Expected behavior
Swagger documentation should get generated similar to packages that don't start with "vendor"
Your swag version
v1.16.3
Your go version
1.21.6
The text was updated successfully, but these errors were encountered:
As info.PackagePath will always have the prefix of the package where swag was run, do we need this check?
If we do can we restrict it to vendor/ paths?
Describe the bug
I was running swag in my package -> vendor-service. But due to a vendor prefix check, all the files are being ignored and swagger docs are not generated.
To Reproduce
Steps to reproduce the behavior:
swag init
docs/swagger.json
does not have the swagger documentation dataExpected behavior
Swagger documentation should get generated similar to packages that don't start with "vendor"
Your swag version
v1.16.3
Your go version
1.21.6
The text was updated successfully, but these errors were encountered: