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
OTEP-66 originally had the propagator interface divided into separate Injectors and Extractors. In OpenTelemetry Ruby we found some advantages to this division. For example, you can have asymmetry in the formats that are injected / extracted, and there are situations where order matters. By dividing Propagators into Injectors and Extractors you can still implement the Propagator and CompositePropagator interfaces by composing individual Injectors and Extractors. This PR updates the api-propagators spec to allow for that possibility.
@mwear would you like to take a look at this and see how it can be applied?
The text was updated successfully, but these errors were encountered:
This doesn't require a change to OpenTemetry JS. It allows propagators to be split into injectors and extractors if it makes sense. You will still have a Propagator (and CompositePropagator) interface, they will just be composed of individual extractors and injectors. If this is something the SIG would like to do, the spec change allows for it, but it's not required.
Link to spec PR: open-telemetry/opentelemetry-specification#578
@mwear would you like to take a look at this and see how it can be applied?
The text was updated successfully, but these errors were encountered: