Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

brio-gen: follow Go standard for generated files #939

Merged
merged 4 commits into from
May 10, 2022

Conversation

dolmen
Copy link
Contributor

@dolmen dolmen commented Apr 27, 2022

One standard exists for Go generated files: https://golang.org/s/generatedcode

This pull request:

  • add .gitignore for files produced by brio-gen tests
  • fixes brio-gen to follow the standard for the files it produces
  • fixes go:generate commands in hbook/hbook.go to run brio-gen from the source (do not require an installed binary)
  • regenerates files in hbook: go generate -run=brio-gen hbook.go

dolmen added 4 commits April 28, 2022 00:03
Fix brio-gen to produce files with the standard Go header for generated
files.
See https://golang.org/s/generatedcode
Fix call to brio-gen command from go:generate to use the local copy of
brio-gen (using "go run") instead of an installed binary that may be outdated.
Files are now generated with the standard Go header for generated files.
See https://golang.org/s/generatedcode

cd hbook; go generate -run=brio-gen hbook.go
@dolmen
Copy link
Contributor Author

dolmen commented Apr 28, 2022

@sbinet I have some further improvement ideas for brio-gen, but I'm waiting for this PR to be merged as it impacts all generated files.

Copy link
Member

@sbinet sbinet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

hbook/hbook.go Show resolved Hide resolved
@sbinet sbinet merged commit 40700b8 into go-hep:main May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants