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
#1212 updated the propagation API to unify the inject and extract parts of propagators given this is assumed the default case.
It is still possible to wrap a propagator in a way that it is only used to inject or extract cross-cutting concerns. This should be captured in an example test to help users understand how to do this if they need this functionality.
The text was updated successfully, but these errors were encountered:
@MrAlias Could you describe a situation where this would be used?
First thing that comes to mind is a translation for B3 based service that runs in an environment where W3C is the standard. I.e. Extract incoming requests that contain B3 headers and only inject W3C headers on outgoing requests.
#1212 updated the propagation API to unify the inject and extract parts of propagators given this is assumed the default case.
It is still possible to wrap a propagator in a way that it is only used to inject or extract cross-cutting concerns. This should be captured in an example test to help users understand how to do this if they need this functionality.
The text was updated successfully, but these errors were encountered: