Golang

2201 readers

12 users here now

This is a community dedicated to the go programming language.

Useful Links:

Rules:

Posts must be relevant to Go
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

founded 1 year ago

MODERATORS

[email protected]

How to affect the order of operations for "go generate" (pkg.go.dev)

submitted 1 year ago by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

Say I have go:generate directives in two files: one in the foo/ directory and one in the mock/ directory. The generated mock code will need data structures from the generated code in the foo module. Will go generate ./... reliably generate code in the correct order? What do I need to do to make that happen?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

I'm a go n00b, but since the source code is available, I figured I'd look. TL;DR: it probably uses the shell's default globbing resolution to produce the file list.

The generate command iterates over the internal files, but I can't find exactly how GoFiles is populated.

You can probably learn what it's doing by running go generate -n or go generate -x, and I think you can also explicitly call go generate with a file pattern list, which would give you this control.

Otherwise, I think you can include more than one magic comment in a single file, so if you have some dependant generators, these could be placed in the same file, sequentially, and you'd get the expected result.

Another alternative would be to try renaming the relevant files so that they sort the way you want them to run, lexicographically.

[–] [email protected] 2 points 1 year ago

Good answers. I like these. I like the more than one command in a file, that will work. And yes, should have read the source!