4 ms·
> There's a couple of repos at work which contain multiple Go modules (each in their own subdirectory, with their own go.mod files). There's almost no reason t
by preseinger 5y ago
> There's a couple of repos at work which contain multiple Go modules (each in their own subdirectory, with their own go.mod files).
There's almost no reason to do this. 1 repo = 1 module. Even for monorepos.
- gkfasdfasdf 5y agoCan you elaborate? What if you have multiple commands (main.go) with differing dependencies?
- preseinger 5y agoThey can (and usually should) exist in a single module. Each compiled artifact will link in only the dependencies it requires, not all of the dependencies of the parent module.