fix(otlp-exporter-base): avoid adding new userAgent option for browser exporters #6013
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.
Which problem is this PR solving?
Follow-up to #5928, as I missed it while doing the review. I noticed this while working on #5994.
The
userAgent
option is not used in any of the browser transports. This PR removes it from theOtlpHttpConfiguration
interface so that it's only present onOtlpNodeHttpConfiguration
andOtlpGrpcConfiguration
where it's actually used. 🙂Skipping changelog since the change from #5928 is unreleased.
cc @david-luna