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
Forgive me if I've missed the docs or ticket that explains this (as it seems fairly fundamental), but I have a base class library which contains common models across several packages, and the models aren't found when generating swagger generate spec. The example says null and none of the fields are detected.
I am within the GOPATH, although the base class module is a relative import like so:
Problem statement
Forgive me if I've missed the docs or ticket that explains this (as it seems fairly fundamental), but I have a base class library which contains common models across several packages, and the models aren't found when generating
swagger generate spec
. The example saysnull
and none of the fields are detected.I am within the GOPATH, although the base class module is a relative import like so:
replace github.com/VigilantApps/core-services/bcl => ../bcl
Is there any workaround to allow me to avoid duplicating code (model definitions) whilst keeping my swagger docs functioning? Thanks for your time.
Swagger specification
// route defined like so:
And when
instance
is defined in the same module, it works fine. But as soon as I move the definition to my bcl module, it stops working:Environment
swagger version:
go version: 1.21
OS: macOS 13.5
The text was updated successfully, but these errors were encountered: