Nate ran into an interesting problem yesterday. If we begin to use go
generate directives to auto-generate code, do we care that this code
doesn't have a Copyright header? We check the generated file into source
control, but as the file is meant to be regenerated in the event of a
change, we do
Can the "thing" that is generating the content not add the header?
On 6 January 2016 at 22:18, Katherine Cox-Buday <
katherine.cox-bu...@canonical.com> wrote:
> Nate ran into an interesting problem yesterday. If we begin to use go
> generate directives to auto-generate code, do we care that this
So, two things:
1.) We don't need to worry about this anymore, since I've removed the need
for the generated code. But to clarify, I was using stringer (
https://github.com/golang/tools/blob/master/cmd/stringer/stringer.go) which
generates files with String() methods for enums.
2.) There's like 10
I agree with Nate that we should not have to use internal
generate tools when external ones will do the job
(stringer is a good example).
We have a similar issue - we're using the stringer tool
in various places, and we also auto-generate API
client code from the server implementation.
We don't a
