On Saturday, February 29, 2020 at 10:03:34 AM UTC-8, Sankar wrote:
>
> I am starting a new project (say `hello`) and I am totally confused about
> what package structure to use. [...]
>
You might find the project-layout notes from the golang-standards GitHub
organization (which seems to be a
1 go.{mod|sum} per repository, no vendoring
tree/
angular-ui/
cmd/
hello-api-server/
hello-cli/
hello-daemon/
internal/
internal-lib1/
internal-lib2/
library1/
library2/
library3/
python-tests/
go.mod
go.sum
On Saturday, 29 February 2020 19:03:34 UTC+1, Sankar wrote:
>
I would avoid multiple go.mod files in one repository as well. I generally
follow the rule of thumb, one module per repository.
On Saturday, 29 February 2020 19:03:34 UTC+1, Sankar wrote:
>
> I am starting a new project (say `hello`) and I am totally confused about
> what package structure to us
ஞாயி., 1 மார்., 2020, முற்பகல் 4:17 அன்று, hartzell
எழுதியது:
> On Saturday, February 29, 2020 at 10:03:34 AM UTC-8, Sankar wrote:
>>
>> I am starting a new project (say `hello`) and I am totally confused about
>> what package structure to use. [...]
>>
>
> You might find the project-layout note
On Tue, Mar 3, 2020, at 10:09, Rizwan Iqbal wrote:
> I would avoid multiple go.mod files in one repository as well. I
> generally follow the rule of thumb, one module per repository.
I generally follow this advice too, however, I make an exception for
modules that don't need to be versioned. For e
