Re: [go-nuts] Go mod ignoring project sub-modules

Aah okay, I've got it working now - thanks! Not going to run tags just to make things easier, but I'll be the sole developer for a good while so it shouldn't be too much of an issue (and it's self-inflicted, if it is)! Thanks again for the assistance On Tuesday, August 17, 2021 at 5:49:32 PM UT

Re: [go-nuts] Go mod ignoring project sub-modules

If you are using submodules, the best way to do that is to treat each modules as a separately versioned, releasable unit. So each module has a "require" directive for other modules it needs at the minimum usable version (managed with 'go get' or 'go mod tidy'). You can tag versions for each submodu

Re: [go-nuts] Go mod ignoring project sub-modules

Thanks for the prompt response, Jay! And thanks for clearing that up, it's good to know that it's intended to run as such. For the purpose and scale of this project, it's a bit easier to keep everything together and use sub-modules where I can (this hasn't been an issue thus far) so I'd like to

Re: [go-nuts] Go mod ignoring project sub-modules

Hi Nic, This is actually working as intended, though I don't think we've adequately documented it. I've sent CL 342531 to mention this in the reference documentation. In short though, files in a subdirectory that contains a go.mod file are c

[go-nuts] Go mod ignoring project sub-modules

Hi all, Hoping someone can give me a bit of assistance here. I'm busy refactoring a gRPC project of mine so that all proto files are generated into a single, "protoFile" directory, instead of having the generated files living under the service's directory. My idea is to have the generated files