[Feature Request] Serialization context for codecs and converters #434
Description
Is your feature request related to a problem? Please describe.
When serializing/deserializing a payload for a workflow or activity users payload codec/converter may want to know details about the payloads context. For example with workflow input/output, the context could include workflow ID. This can be useful if the users want to sign the payload with the workflowID to help protect against replay attacks.
Describe the solution you'd like
A solution similar to the Java SDK in other languages, see temporalio/sdk-java#1695. Also, make sure that the async activity client gets this context too. Note, this information needs to be available to converters too e.g. for outbound client calls, so it's not just for codecs.
Per-SDK Tickets
- Go - Context aware data converters cannot get IDs of outbound activities and child workflow sdk-go#1352
- Java - Already exists - Provide SerializationContext for PayloadConverter and PayloadCodec sdk-java#1695
- Core - N/A
- TypeScript - [Feature Request] Serialization context for codecs and converters sdk-typescript#1661
- Python - [Feature Request] Serialization context for codecs and converters sdk-python#796
- .NET - [Feature Request] Serialization context for codecs and converters sdk-dotnet#438
- Ruby - [Feature Request] Serialization context for codecs and converters sdk-ruby#238
- PHP - [Feature Request] Serialization context for codecs and converters sdk-php#587
- Temporal CLI - N/A