-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Format generated test code #10899
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
My bigger concern is why linter isn't firing for this use case. Submitted open-telemetry/opentelemetry-collector-contrib#30439 |
Sounds like a good idea to me, and the concern regarding the linter not running has been answered. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
transferred issue as mdatagen lives in the core repo now |
Component(s)
cmd/mdatagen
Describe the issue you're reporting
See open-telemetry/opentelemetry-collector-contrib#30425 (comment) and open-telemetry/opentelemetry-collector-contrib#30419 (comment)
Generated code is not formatted. We can run gofmt explicitly on the generated code when we generate the test.
The text was updated successfully, but these errors were encountered: