I found that some packages, say github.com/gcash/bchwallet/walletdb, are placed in submodule github.com/gcash/bchwallet/walletdb instead of root module.
However, it seems that submodule github.com/gcash/bchwallet/walletdb is not tagged. According to go docs, submodule should be tagged like relative-path-to-root/vX.X.X.
At now, when trying to import package github.com/gcash/bchwallet/walletdb, downstream would depends on pseudo-version of module github.com/gcash/bchwallet/walletdb.
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, walletdb/v0.0.1, walletdb/v0.10.0etc, so that other project can use tag to import this module in go.mod.
I found that some packages, say
github.com/gcash/bchwallet/walletdb, are placed in submodulegithub.com/gcash/bchwallet/walletdbinstead of root module.However, it seems that submodule
github.com/gcash/bchwallet/walletdbis not tagged. According to go docs, submodule should be tagged likerelative-path-to-root/vX.X.X. At now, when trying to import packagegithub.com/gcash/bchwallet/walletdb, downstream would depends on pseudo-version of modulegithub.com/gcash/bchwallet/walletdb.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,
walletdb/v0.0.1,walletdb/v0.10.0etc, so that other project can use tag to import this module in go.mod.