<p>Hi all,</p>
<p>I decided to learn programming with Go. I would like to make my first app something useful for community. </p>
<p>So, i created the package "articletext" to extract useful (primary) content text from a html page. A function analyses a html code and drops everything related to navigation, advertising etc. Extracts only useful contents of a document, text of a central element.</p>
<p>But, i am more interested in your feedback about a programming style. What mistakes did i do? What can be done better in terms of code organization, commenting and "best practices"?</p>
<p>There is my package <a href="https://github.com/Gelembjuk/articletext" rel="nofollow">https://github.com/Gelembjuk/articletext</a></p>
<hr/>**评论：**<br/><br/>mwholt: <pre><p>Nice job!</p>
<p>I'd suggest writing some tests. <a href="https://golang.org/pkg/testing" rel="nofollow">https://golang.org/pkg/testing</a> will help with that.</p>
<p>I'd also suggest looking at the lint warnings; learn to conform to godoc specifications. Here are the lint warnings: <a href="https://goreportcard.com/report/github.com/Gelembjuk/articletext" rel="nofollow">https://goreportcard.com/report/github.com/Gelembjuk/articletext</a></p>
<p><a href="https://github.com/Gelembjuk/articletext/blob/2023e034759d51e7466c18a80eaf40146aedd81b/articletext.go#L48-L49" rel="nofollow">These error handling lines</a> should lose the log.Fatal, which terminates the program.</p></pre>beertocode: <pre><p>A good way to have a quick check on your code is to use go report card:
<a href="https://goreportcard.com/report/github.com/Gelembjuk/articletext" rel="nofollow">https://goreportcard.com/report/github.com/Gelembjuk/articletext</a></p>
<p>Better: Use golint or better gometalinter everytime before you commit new code.</p>
<p>Handle errors gracefully. You are using <code>log.Fatal</code> in most error conditions, which will exit the program immediately, instead of returning the error.</p></pre>
