Skip to content

Improving generated Go code to comply with go lint rules, in order …#34

Open
derFunk wants to merge 1 commit into
gnewton:masterfrom
derFunk:master
Open

Improving generated Go code to comply with go lint rules, in order …#34
derFunk wants to merge 1 commit into
gnewton:masterfrom
derFunk:master

Conversation

@derFunk
Copy link
Copy Markdown

@derFunk derFunk commented Jul 27, 2018

…to avoid massive warnings from generated code:

  • Avoid excessive underscores in names, instead use CamelCase.
  • Add comments to public structs to avoid warnings about missing ones.
  • Use uppercase representations for common initialisms (there are more, not yet integrated here: https://github.com/golang/lint/blob/master/lint.go#L749)
  • Setting default value of keepXmlFirstLetterCase to false, because it's enabled by setting the -K cli argument.

…to avoid massive warnings from generated code:

- Avoid excessive underscores in names, instead use CamelCase.
- Add comments to public structs to avoid warnings about missing ones.
- Use uppercase representations for common initialisms (there are more, not yet integrated here: https://github.com/golang/lint/blob/master/lint.go#L749)
- Setting default value of `keepXmlFirstLetterCase` to `false`, because it's enabled by setting the `-K` cli argument.
@gnewton
Copy link
Copy Markdown
Owner

gnewton commented Jul 30, 2018

I will take a look at this over the next few days :-)

Thanks,
Glen

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