Avoid unkeyed fields usage for exported struct in generated code #683
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This updates Go code template to avoid unkeyed fields usage for exported struct.
I'm using
generate-fixcommand to generate my own custom FIX application.However, Go standard linter,
go vet, raises an alert because the generated Header/Trailer struct literal uses unkeyed fields.https://github.com/golang/tools/blob/master/go/analysis/passes/composite/composite.go
While I understand the unkeyed field usage is valid for generated code, it can be somewhat inconvenient to exclude generated code from vet target or disable composite analysis entirely by
go vet -composites=false ./....It would be preferable if the generated code adhered to the recommended style to avoid such issues.