go-dbf icon indicating copy to clipboard operation
go-dbf copied to clipboard

Consider tagging module "godbf"?

Open Rick-xuy opened this issue 2 years ago • 0 comments

I found that package github.com/LindsayBradford/go-dbf/godbf is placed in submodule github.com/LindsayBradford/go-dbf/godbf instead of root module.
However, it seems that submodule github.com/LindsayBradford/go-dbf/godbf is not tagged. According to Go Modules wiki, submodule should be tagged like relative-path-to-root/vX.X.X. At now, when trying to import package github.com/LindsayBradford/go-dbf/godbf, downstream would depends on pseudo-version of module github.com/LindsayBradford/go-dbf/godbf.

github.com/LindsayBradford/go-dbf/godbf v0.0.0-20220427112540-117aaf115530

I think it is not very readable and difficult to upgrade. This is not conductive to version control either. So, I propose whether it is possible to tag submodule properly. For example, godbf/v0.0.1, godbf/v1.0.0etc, so that other project can use tag to import this module in go.mod.

Rick-xuy avatar Feb 18 '23 03:02 Rick-xuy