Skip to content

Fix function comments based on best practices from Effective Go #235

Open
CodeLingoBot wants to merge 1 commit into
ant0ine:masterfrom
CodeLingoBot:rewrite
Open

Fix function comments based on best practices from Effective Go #235
CodeLingoBot wants to merge 1 commit into
ant0ine:masterfrom
CodeLingoBot:rewrite

Conversation

@CodeLingoBot
Copy link
Copy Markdown

@CodeLingoBot CodeLingoBot commented Feb 13, 2019

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared.
From effective go.

PR generated by CodeLingo. Install here to drive Continuous Higher Standards.

Signed-off-by: CodeLingo Bot <bot@codelingo.io>
@BlakeMScurr
Copy link
Copy Markdown

Hi @ant0ine and go-json-rest contributers,

@BlakeMScurr from CodeLingo here. This PR is testing out a new service. I'd love to hear your feedback or answer your questions. We're keen to learn how we can best help dev teams without getting in your way.

@BlakeMScurr & the CodeLingo Team

@BlakeMScurr
Copy link
Copy Markdown

BlakeMScurr commented Feb 13, 2019

@ant0ine how valuable do you find these changes? You should pass golint now - is that worth much to you? How much better would it be if all the changes were like https://github.com/ant0ine/go-json-rest/pull/234/files#diff-541659943e3a6411fa01bdaa15aba143R53, rather than just adding a colon after the function name?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants