From 63168c238f87aa4bcee9ebf824304f023948e04b Mon Sep 17 00:00:00 2001 From: Laurent Demailly Date: Sun, 20 Oct 2024 09:01:13 -0700 Subject: [PATCH] Update 2024-10-19-no-nonsense-go-package-layout.md IDE typo --- docs/_posts/2024-10-19-no-nonsense-go-package-layout.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_posts/2024-10-19-no-nonsense-go-package-layout.md b/docs/_posts/2024-10-19-no-nonsense-go-package-layout.md index d21f816..38344eb 100644 --- a/docs/_posts/2024-10-19-no-nonsense-go-package-layout.md +++ b/docs/_posts/2024-10-19-no-nonsense-go-package-layout.md @@ -57,7 +57,7 @@ Any package you put into a pkg directory can be moved the root. Some people think that having packages at the top, "clutters", the directory... first what does get cluttered if you add unnecessary directory layers is every single import in dozen of files and possibly hundreds of dependencies... think about them... Second, feel free to move the various docs etc to some subdirectory. Lastly what is 'clutter' navigation probably comes through your "godoc" (the excellent [pkg.go.dev](https://pkg.go.dev/) or your self hosted equivalent for private repositories). -Btw don't get me started with repos that have dozens of files and that to see what is going on not using an idea you have to go main.go -> some other file -> some init file -> some start function -> some other files... while all this could be in 1 or 2 places, easier to follow and find. +Btw don't get me started with repos that have dozens of packages and files and where to see what is going on without an IDE you have to go: main.go -> some other file -> some init file -> some start function -> some other files... while all this could be in 1 or 2 places, easier to follow and find. #### util/