Closed im-kulikov closed 5 years ago
Hi, yes this was misleading, since the tag was created before renaming. Just recently made another tag v1.3.3
in order to prevent these misunderstandings in the future, caused by migration to module.
Thanks..
I think this is still an issue:
λ go get -u gopkg.in/DATA-DOG/go-sqlmock.v1
go: gopkg.in/DATA-DOG/go-sqlmock.v1@v1.3.3: go.mod has non-....v1 module path "github.com/DATA-DOG/go-sqlmock" at revision v1.3.3
go get: error loading module requirements
Should go.mod
record the fully qualified module name, i.e., gopkg.in/DATA-DOG/go-sqlmock.v1
?
Hi @jeffreylo we cannot rely making module name as gopkg.in, that service may just go away any time. Use github.com/DATA-DOG/go-sqmock
for go get and anything else.
Problem with module naming here from commit
In documentation: