Non-template propagator, Implement Global Propagator, no-op propagator #668
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.
Fixes #540
Changes
Please provide a brief description of the changes here.
In continuation with discussion in Add Global Propagator, Noop Propagator #644, remove the templatized propagator class, so that the propagator is not compiled against its carrier/target type, and the carrier/target type is instead passed as
TextMapCarrier
object in Inject() and Extract() functions. This further allows not to create global/composite propagator per carrier/target type. As an example, a global propagator once set, can be used to extract the context from (say) gRPC response, and pass the context to (say) HTTP request.Provide an implementation of global and No-op propagator.
For significant contributions please make sure you have completed the following items:
CHANGELOG.md
updated for non-trivial changes