Interface: NexusSerializationContext
Experimental
Context provided to data converters for payloads of a Nexus operation.
Callers receive this context when encoding inputs and decoding results or failures. Handlers receive it when decoding inputs, encoding synchronous results, and encoding failures raised while handling a Nexus task. It is not propagated to a handler that completes an operation asynchronously.
A standalone operation handle uses the context of its start request, including when the start request returns an already-running operation; a handle obtained by operation ID without starting an operation has no endpoint, service, or operation information to build a context from and therefore serializes without one.
A failure encoded by a handler is later decoded by a caller, and some operation paths lack this context entirely. Contextual encodings must therefore be self-describing, and decoders must keep accepting payloads encoded without context.
Serialization context is an experimental feature and may change.
Properties
endpoint
endpoint:
string
Experimental
Nexus endpoint name.
operation
operation:
string
Experimental
Nexus operation name.
service
service:
string
Experimental
Nexus service name.
type
type:
"nexus"
Experimental
Always 'nexus' for Nexus operation payloads.