<p>Hello, please could you take a look at the following Go project and let me know whether this is a good way of structuring my project.
<a href="https://github.com/drum445/vehicleFinder" rel="nofollow">https://github.com/drum445/vehicleFinder</a></p>
<p>I struggle finding the best way to do this as I come from a MVC background, but would like to stick to the repo pattern if it works.</p>
<p>Appreciate it</p>
<hr/>**评论：**<br/><br/>ui7_uy8: <pre><blockquote>
<p>I come from a MVC background</p>
</blockquote>
<p>The first thing I see is that you don't even stick to the basics [1]. There is no need for a src folder or a doc folder [2]</p>
<p>[1] <a href="https://golang.org/doc/code.html" rel="nofollow">https://golang.org/doc/code.html</a></p>
<p>[2] <a href="https://blog.golang.org/godoc-documenting-go-code" rel="nofollow">https://blog.golang.org/godoc-documenting-go-code</a></p>
<p>The real issue is the complete lack of tests.</p></pre>drum445: <pre><p>Thanks but I meant more of the package structure, the doc and src I know can be removed.
Tests will come later, this is simply a structure excersise
Does the separation of packages look correct?</p></pre>
