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
compile errors regarding: v1.POST undefined (type *echo.Group has no field or method POST, but does have Post) e.Start undefined (type *echo.Echo has no field or method Start)
This was weird to me at first because I knew that echo had a POST function on it's groups. Checked though and noticed that I'm using Echo v2 not v1 while vgo fetched v1 as the dependency.
the import path is obviously "github.com/labstack/echo", note that v1 does exist in the code as the name for the echo.Group that the POST endpoint in the first error is attached to.
vgo list -m -u shows echo as current (cause for v1 it is)
The package also may need modifications to completely support vgo, as vgo allows v1 and v2+ to be used together. So for singletons there will be 2+ instances. Hence why vgo forces you to have a go.mod file for v2+.
What version of Go are you using (
go version
)?go1.10
What operating system and processor architecture are you using (
go env
)?linux/amd64
What did you do?
I added a
go.mod
file to an existing project and ran vgo build. After correcting a missing dependency the following require lines are present.What did you expect to see?
the application to be compiled into a binary
What did you see instead?
compile errors regarding:
v1.POST undefined (type *echo.Group has no field or method POST, but does have Post)
e.Start undefined (type *echo.Echo has no field or method Start)
This was weird to me at first because I knew that echo had a POST function on it's groups. Checked though and noticed that I'm using Echo v2 not v1 while vgo fetched v1 as the dependency.
the import path is obviously
"github.com/labstack/echo"
, note thatv1
does exist in the code as the name for the echo.Group that the POST endpoint in the first error is attached to.vgo list -m -u
shows echo as current (cause for v1 it is)Attempting to upgrade has interesting behavior as well:
The text was updated successfully, but these errors were encountered: