Which echo?

[siredwin]

I realized that my old import "github.com/labstack/echo" still works, but I see "github.com/labstack/echo/v4" in the examples. Which one do I use? I need some clarity. Or is that using a specific version?
Also, how did the forums get that bad? It used to be fun.

[lammel]

As Echo is using the Go way of handling modules you need to specify the version.

So for the current latest version use import "github.com/labstack/echo/v4".
The docs have been updated recently, so this is usally the best place to start looking.

[lammel]

You have to use the imports github.com/labstack/echo/v4 and github.com/labstack/echo/v4/middleware in all your code.
Don't mix github.com/labstack/echo/v4 with the outdated github.com/labstack/echo

Please provide a code sample if you still think you get something wrong with modules. Maybe you found an issue in the echo documentation.

[siredwin]

It is working now! I guess I was confused because go get -u github.com/labstack/echo/... still works perfectly.

[lammel]

This is not the correct way and will give you an outdated version of echo (namely v3.3.10, our last release not supporting go modules, which were introduced in Go 1.11 and are now the Go way to handle dependencies.

I guess the documentation needs another update.

Please only use github.com/labstack/echo/v4for setup with go get and when importing in your application.

[siredwin]

Please check that again! It pulls the latest v4.1.17. That was part of the confusion. But I do get it. It makes sense with modules.

[lammel]

Thanks will check that.

using import "github.com/labstack/echo"`

I was referring to your above comment actually.
Just be sure to use github.com/labstack/echo/v4 (absolutely important to use v4 here).

Enjoy echo! ;-)