2 ms·
You can store Go files in src/ if you really want, nothing really stopping you, but it's not the usual approach, no. Tests are usually stored next to the actual
by arp242 6y ago
You can store Go files in src/ if you really want, nothing really stopping you, but it's not the usual approach, no. Tests are usually stored next to the actual implementations rather than a tests/ directory.
In which directory to store files is an incredibly small and minor detail though.
- linkdd 6y ago> nothing really stopping you, but it's not the usual approach In my experience, if you open-source a project, it better have to follow conventions. Following conventions makes sure someone else can read your code easily. > In which directory to store files is an incredibly small and minor detail though. Yeah it's a small detail, but it is important to me to not get lost in a directory tree. Random example taken from a github search: https://github.com/gofiber/fiber https://github.com/gofiber/fiber Is it really ok to have that much source code at the toplevel? Is the code architecture clear at a glance? For me, it is not, and I'll have to put in extra work (I'm lazy) to understand the code and how it works. I don't mind doing that for other projects, but for my projects as I work on them daily, it becomes a pain very quickly.