<p>I was planning on writing a package that would automate creating json according to the Google JSON Style guide.</p>
<p><a href="https://google-styleguide.googlecode.com/svn/trunk/jsoncstyleguide.xml" rel="nofollow">https://google-styleguide.googlecode.com/svn/trunk/jsoncstyleguide.xml</a></p>
<p>I did not want to recreate the wheel, so I wanted to check if anyone knew of a package out there already.</p>
<p>Also I wanted to know if there were any feature requests.
Some things I was going to add were:</p>
<p>An error code registry</p>
<p>Setting Defaults for service</p>
<p>Automatic writing Marshaling and writing to ResponseWriter and Unmarshaling from Response. </p>
<p>Thoughts?
I would also be willing to collaborate, if someone wanted to work on this as well?</p>
<hr/>**评论：**<br/><br/>binaryblade: <pre><p>umm, enocding/json is in the stdlib.</p></pre>jasonrichardsmith: <pre><p>The structure of this API response style is not.</p>
<p>Now you could recreate this structure and reuse it personally, or I/we could develop a community package.</p></pre>: <pre><p>[deleted]</p></pre>jasonrichardsmith: <pre><p>I think you are misreading the intention. The intention is not to provide correctly structured json, the intention is to provide json responses in accordance with the style guide. Meaning having values stored in a standardized fashion in accordance withe the style guide.</p></pre>BoTuLoX: <pre><p>I'm going to guess your intent is readability. Why not simply use YAML?</p></pre>michaelbironneau: <pre><p>Interesting idea, but just glancing over the style guide you'll need users of your library to provide lots of additional information (eg. <code>error.domain</code>) instead of just passing you an <code>error</code>, for example. By the time a developer is done understanding what all this information means, they've already read the style guide and they might as well use encoding/json to do the same thing without introducing another dependency into their work.</p>
<p>One way you could make this useful to a general audience is if it could plug into an existing ORM-to-REST builder such as go-json-rest, because then you might have some of this information already, but I'm not sure how feasible that is.</p></pre>jasonrichardsmith: <pre><p>I wasn't building a robust tool, I am just building an easy structure anyone can import or fork. Got most of it written already.</p>
<p><a href="https://github.com/jasonrichardsmith/google_json_style" rel="nofollow">https://github.com/jasonrichardsmith/google_json_style</a></p></pre>
