cybercyst/project-layout
1
0
Fork 0
mirror of https://github.com/golang-standards/project-layout.git synced 2025-05-05 15:43:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated the README.md file by adding a paragraph that provides further clarification on the purpose of the 'internal' directory.

Browse Source
This commit is contained in:
anazibinurasheed 2023-09-06 13:35:43 +05:30
parent 2d1e32a7e0
commit 0bfa73e2ba
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -68,7 +68,7 @@ Private application and library code. This is the code you don't want others imp
You can optionally add a bit of extra structure to your internal packages to separate your shared and non-shared internal code. It's not required (especially for smaller projects), but it's nice to have visual clues showing the intended package use. Your actual application code can go in the `/internal/app` directory (e.g., `/internal/app/myapp`) and the code shared by those apps in the `/internal/pkg` directory (e.g., `/internal/pkg/myprivlib`).
You use internal directories to make packages private. If you put a package inside an internal directory, then other packages can’t import it unless they share a common ancestor. It’s the only directory named in Go’s documentation and has special compiler treatment.
You use internal directories to make packages private. If you put a package inside an internal directory, then other packages can’t import it unless they share a common ancestor. And it’s the only directory named in Go’s documentation and has special compiler treatment.
### `/pkg`