Currently we represent effects in non-standard format that uses links to ImpliedInvocationModel as opposed InstructionModel. We do such a representation because we do not have an invocation spec implemented yet and most things expect ImpliedInvocationModel in place if invocations & instructions.

Hierarchy

  • EffectsModel

Properties

Properties

fork: readonly Link<ImpliedInvocationModel<Capability<Ability, `${string}:${string}`, unknown>>, number, number, 1>[]
join?: Link<ImpliedInvocationModel<Capability<Ability, `${string}:${string}`, unknown>>, number, number, 1>

Generated using TypeDoc