refactor: OpenTracingPropagator -> OTTracePropagator rename #329
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?
This PR renames the OpenTracingPropagator to OTTracePropagator as per this spec issue: open-telemetry/opentelemetry-specification#1391, specifically this comment: open-telemetry/opentelemetry-specification#1391 (comment). As discussed in the issue, there was not a single context propagation format specified in OpenTracing, but there were several that gained some adoption. The OT trace format was adopted by Lightstep and was also used by the "basic tracer" implementations in OpenTracing.
Short description of the changes
OpenTracingPropagator
toOTTracePropagator
opentelemetry-propagator-opentracing
toopentelemetry-propagator-ot-trace