Skip to content

Properly define CorrelationContext as an optional interface. #482

@carlosalberto

Description

@carlosalberto

From #420

It is not clear to me why we choose to not have all the functions interact explicitly with a "CorrelationContext" object and we want this path of interacting explicitly with Context. In my opinion this case is more natural for languages that explicitly pass Context around (like Go) but not that natural for Python where for example the ContextVar library does not work very well with this API.

This is a very important distinction that we want to make so languages keep a certain uniformity, and I do agree this the statement above, so we must add a note or a section that fully clarifies this one.

Metadata

Metadata

Assignees

Labels

area:apiCross language API specification issuepriority:p2Medium priority levelrelease:allowed-for-gaEditorial changes that can still be added before GA since they don't require action by SIGsspec:baggageRelated to the specification/baggage directory

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions