Closed bufdev closed 7 years ago
Also for example, scripts/updateLicenses.sh
is called like 4 times, since I'm assuming this was done any time a new dependency graph came up (and it's not working right now properly) :)
@peter-edge that sounds reasonable 👍
@breerly We might want to get this in then sooner than later https://github.com/yarpc/yarpc-go/pull/632 I just did a merge from upstream and there was already another //go:generate
added, the branch passes make test etc, and I verified 'make generate' does nothing differently than the existing make generate
.
@abhinav seemed to have some reservations - can you elaborate on those here?
Way back in the day when the original blog post came out, I loved the idea and started using
go generate
a bunch, but then as I got older I started to dislike shell commands being declared in various files, and having failures when programs weren't installed. I moved everything to my Makefiles, which was the SOT for everything else development related, and it made sense that generation should go there too. It made my life a lot easier to know what was really happening just by looking at one file, and knowing the invocation order without having to think about package dependencies.Would this be something that could potentially be done here? I basically am advocating for moving all these to a
generate
target: