DisplayReactorParameters
Defined in: core/src/types/display-reactor.ts:62
Extends
Section titled “Extends”Type Parameters
Section titled “Type Parameters”A = BaseActor
Properties
Section titled “Properties”validators?
Section titled “validators?”
optionalvalidators?:Partial<{ [M in string]: DisplayValidator<A, M> }>
Defined in: core/src/types/display-reactor.ts:69
Optional initial validators to register. Validators receive display types (strings for Principal, bigint, etc.)
clientManager
Section titled “clientManager”clientManager:
ClientManager
Defined in: core/src/types/reactor.ts:71
Inherited from
Section titled “Inherited from”ReactorParameters.clientManager
name:
string
Defined in: core/src/types/reactor.ts:72
Inherited from
Section titled “Inherited from”idlFactory
Section titled “idlFactory”idlFactory: (
IDL) =>any
Defined in: core/src/types/reactor.ts:73
Parameters
Section titled “Parameters”any
Returns
Section titled “Returns”any
Inherited from
Section titled “Inherited from”canisterId?
Section titled “canisterId?”
optionalcanisterId?:CanisterId
Defined in: core/src/types/reactor.ts:74
Inherited from
Section titled “Inherited from”pollingOptions?
Section titled “pollingOptions?”
optionalpollingOptions?:PollingOptions
Defined in: core/src/types/reactor.ts:84
How update calls poll read_state for their result. The reactor passes
this one object to every update call, so a strategy here is shared by
all of them. Use createPollingStrategy, which keeps each request’s
state apart, or leave strategy out to get a fresh defaultStrategy()
per request. A strategy from @icp-sdk/core/agent such as
defaultStrategy() serves a single request: pass it per call through
callConfig.pollingOptions instead.