Avoid breaking developer builds during gen-code integration #334
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Various changes made in the
gen-code
branch not only produce additionala_*code.go
files, but change the waya_*data.go
files are generated.So it's best to start with a clean slate before running
go generate ./...
, to prevent it picking up those stale files.Another approach to this could be to use build tags so
go generate
-run tools don't pick up anya_*.go
files at all, but this seems easier and more effective.