Option to expose proto enum constants with proper Go style

ruiaylin / goprotobuf

Automatically exported from code.google.com/p/goprotobuf

Other

0 stars 0 forks source link

Option to expose proto enum constants with proper Go style #59

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Currently proto CONSTANTS_LIKE_THIS are being exposed as such within Go code 
instead of translating to camelCase like message names. This is causing golint 
to freak out.

An option (or change to the generated files) to generate golint-friendly code 
would be great.

Original issue reported on code.google.com by andyb...@chromium.org on 11 Nov 2014 at 7:51

GoogleCodeExporter commented 9 years ago

It's unfortunate, but it's historic baggage and generally what people expect.

The solution to your golint problem is to not run golint on generated code.

Original comment by dsymo...@golang.org on 11 Nov 2014 at 7:53

Changed state: Unfortunate