temporalio / temporalio/sdk-typescript
[Feature Request] Run headers through codec
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 917
- Forks
- 224
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 43
Description
As discussed on slack: by default, don't put headers through codec / custom data converter, except for otel baggage.
Putting otel baggage through the codec requires passing contextual info to Codec.encode/decode. And if we're going to do that, perhaps we want to allow users to have the codec be run on their other headers?
Additional context
For future reference, setBaggage returns a new context:
import { context, propagation } from '@opentelemetry/api';
const baggage = propagation.createBaggage({ test: { value: 'true' } });
const newContext = propagation.setBaggage(context.active(), baggage);
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Codec.encode/decode entry points and the header propagation path, then review how setBaggage creates the context. Establish tests for default header handling, OpenTelemetry baggage, and any opt-in conversion; done means the intended behavior is specified and covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100