You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In #11232 I missed a spot where "metadata" is still being passed instead of the correct package name. This would cause a faulty generation when using the generated_package_name feature.
Steps to reproduce
Off of 388bae7 (this is not in a released version of mdatagen), generate a package with a custom name. generated_status.go will have the wrong package name (metadata instead of the intended generated_package_name).
Additional context
As previously mentioned, this bug is not present in a released version of mdatagen yet.
The text was updated successfully, but these errors were encountered:
Describe the bug
In #11232 I missed a spot where
"metadata"
is still being passed instead of the correct package name. This would cause a faulty generation when using thegenerated_package_name
feature.opentelemetry-collector/cmd/mdatagen/internal/command.go
Lines 83 to 86 in 388bae7
Steps to reproduce
Off of 388bae7 (this is not in a released version of mdatagen), generate a package with a custom name.
generated_status.go
will have the wrong package name (metadata
instead of the intendedgenerated_package_name
).Additional context
As previously mentioned, this bug is not present in a released version of
mdatagen
yet.The text was updated successfully, but these errors were encountered: