Skip to content

[exporter/mezmoexporter] unexport mezmo structs #24842

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

Merged
merged 3 commits into from
Aug 3, 2023

Conversation

atoulme
Copy link
Contributor

@atoulme atoulme commented Aug 3, 2023

Those structs don't need to be exported as part of the Go API.

@atoulme atoulme requested a review from dashpole as a code owner August 3, 2023 15:38
@atoulme atoulme requested a review from a team August 3, 2023 15:38
@dmitryax
Copy link
Member

dmitryax commented Aug 3, 2023

After merging few similar PRs, I released that these are breaking api changes. Given that we now have a separate changelog for API, we should utilize it. @atoulme can you please add changelog entry for this one and for others?

@atoulme
Copy link
Contributor Author

atoulme commented Aug 3, 2023

This one needs a changelog for sure. Do we need it for others where it's only test code?

@atoulme atoulme changed the title [chore] unexport mezmo structs [exporter/mezmoexporter] unexport mezmo structs Aug 3, 2023
@dmitryax
Copy link
Member

dmitryax commented Aug 3, 2023

Do we need it for others where it's only test code?

Technically yes. They can potentially still be used outside.

@atoulme
Copy link
Contributor Author

atoulme commented Aug 3, 2023

Alright I will create a separate PR for all the changelogs I missed.

@dmitryax dmitryax merged commit f4f04fe into open-telemetry:main Aug 3, 2023
@github-actions github-actions bot added this to the next release milestone Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants