mirror of
https://github.com/hanzoai/tasks.git
synced 2026-10-04 02:04:03 +00:00
Roey BermanandGitHub
9a65ecdb76
## What changed? - Allow using `chasm.Context` when accessing `MSPointer` - Embed `MSPointer` in the `Workflow` component to allow callbacks to access the exposed mutable state method - Delete `hsm_invocation` to eliminate dead code - Don't wrap CHASM callback failures in `UnprocessableTask` errors, failed callbacks are not supposed to bubble back to the executor anyways
26 lines
978 B
Go
26 lines
978 B
Go
package chasm
|
|
|
|
import (
|
|
"go.temporal.io/server/common/nexus/nexusrpc"
|
|
)
|
|
|
|
// MSPointer is a special CHASM type which components can use to access their Node's underlying backend (i.e. mutable
|
|
// state). It is used to expose methods needed from the mutable state without polluting the chasm.Context interface.
|
|
// When deserializing components with fields of this type, the CHASM engine will set the value to its NodeBackend.
|
|
// This should only be used by the Workflow component.
|
|
type MSPointer struct {
|
|
backend NodeBackend
|
|
}
|
|
|
|
// NewMSPointer creates a new MSPointer instance.
|
|
func NewMSPointer(backend NodeBackend) MSPointer {
|
|
return MSPointer{
|
|
backend: backend,
|
|
}
|
|
}
|
|
|
|
// GetNexusCompletion retrieves the Nexus operation completion data for the given request ID from the underlying mutable state.
|
|
func (m MSPointer) GetNexusCompletion(ctx Context, requestID string) (nexusrpc.OperationCompletion, error) {
|
|
return m.backend.GetNexusCompletion(ctx.getContext(), requestID)
|
|
}
|