<p>So seeing as how this is my first attempt at writing an app in GO I decided to keep the problem domain simple. </p>
<p>This is a very cliche service which exposes a TODO API.</p>
<p>It was written using a layered object oriented design approach.</p>
<p>Given that the language lends itself well to procedural programming, I was hoping to receive some feedback from the community regarding this design decision and whether they feel that it's easier to read. </p>
<p><a href="https://github.com/schweppesale/todo" rel="nofollow">https://github.com/schweppesale/todo</a></p>
<hr/>**评论：**<br/><br/>shovelpost: <pre><blockquote>
<p>layered object oriented design approach</p>
</blockquote>
<p>This structure and naming looks almost exactly like my first Go application (I have Java background).</p>
<p>While this structure works, it's really not ideal for Go.</p>
<p>Please read Ben Jonhson's article about <a href="https://medium.com/@benbjohnson/standard-package-layout-7cdbc8391fc1" rel="nofollow">standard package layout</a>.</p></pre>Schweppesale: <pre><p>Thanks. I'll check this out later tonight.</p></pre>nstratos: <pre><p>I've also passed from this phase when writing my first Go code. </p>
<p>Please read <a href="https://www.reddit.com/r/golang/comments/56wk4v/structuring_go_api/d8n4axl/" rel="nofollow">my answer on a similar question</a> as I have assembled quite a few resources that you might find useful.</p></pre>Schweppesale: <pre><p>You're the man. Thank you.</p></pre>md2perpe: <pre><p>Instead of </p>
<pre><code> switch {
case request.Method == "GET":
</code></pre>
<p>use</p>
<pre><code> switch request.Method {
case "GET":
</code></pre></pre>lilgnomeo: <pre><p>Almost unbearable to read, sorry.</p></pre>allhatenocattle: <pre><p>Why not give feedback that is helpful? </p>
<p>If you can't, what is the point of your message?</p></pre>
