|
|
@@ -53,7 +53,7 @@ It's also a way to group Go code in one place when your root directory contains |
|
|
|
|
|
|
|
|
See the [`/pkg`](pkg/README.md) directory if you want to see which popular Go repos use this project layout pattern. This is a common layout pattern, but it's not universally accepted and some in the Go community don't recommend it. |
|
|
See the [`/pkg`](pkg/README.md) directory if you want to see which popular Go repos use this project layout pattern. This is a common layout pattern, but it's not universally accepted and some in the Go community don't recommend it. |
|
|
|
|
|
|
|
|
Ok not to use it if your app project is really small and where an extra level of nesting doesn't add much value (unless you really want to :-)). Think about it when it's getting big enough and your root directory gets pretty busy (especially if you have a lot of non-Go app components). |
|
|
|
|
|
|
|
|
It's ok not to use it if your app project is really small and where an extra level of nesting doesn't add much value (unless you really want to :-)). Think about it when it's getting big enough and your root directory gets pretty busy (especially if you have a lot of non-Go app components). |
|
|
|
|
|
|
|
|
### `/vendor` |
|
|
### `/vendor` |
|
|
|
|
|
|
|
|
|