lightair/project-layout
1
0 Fork 0
mirror of https://github.com/golang-standards/project-layout.git synced 2026-11-11 23:07:50 +03:00
Code Issues Projects Releases Wiki Activity

more pkg and internal notes

Browse Source
This commit is contained in:
Kyle Quest committed 2019-10-03 14:29:31 -07:00
1 parent 77a030591b
commit 7b4b0889c2
3 files changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

pkg/README.md
+1 -1
View File
@@ -1,6 +1,6 @@
# `/pkg`
Library code that's ok to use by external applications (e.g., `/pkg/mypubliclib`). Other projects will import these libraries expecting them to work, so think twice before you put something here :-)
Library code that's ok to use by external applications (e.g., `/pkg/mypubliclib`). Other projects will import these libraries expecting them to work, so think twice before you put something here :-) Note that the `internal` directory is a better way to ensure your private packages are not importable because it's enforced by Go. The `/pkg` directory is still a good way to explicitly communicate that the code in that directory is safe for use by others.
It's also a way to group Go code in one place when your root directory contains lots of non-Go components and directories making it easier to run various Go tools (as mentioned in these talks: [`Best Practices for Industrial Programming`](https://www.youtube.com/watch?v=PTE4VJIdHPg) from GopherCon EU 2018, [GopherCon 2018: Kat Zien - How Do You Structure Your Go Apps](https://www.youtube.com/watch?v=oL6JBUk6tj0) and [GoLab 2018 - Massimiliano Pippi - Project layout patterns in Go](https://www.youtube.com/watch?v=3gQa1LWwuzk)).