Expand description
Side-effect primitives for async operations.
Reducers are pure functions – they must not perform I/O. When a reducer
needs to trigger an HTTP request, read a file, or show a system alert, it
pushes an EffectEnvelope through the Effects builder.
The platform executor fulfils the effect outside the deterministic core and
dispatches the on_ok / on_err callback actions back into the pipeline.
Structs§
- Effect
Envelope - A queued effect with optional success/failure callbacks.
- ReqId
- An opaque request identifier assigned to each emitted effect.
- Resource
Id - An opaque handle to a platform-managed resource (e.g. a large binary blob).
Enums§
- Action
Input - Extra input data passed alongside an action dispatch.
- Effect
- A side-effect emitted by a reducer.
- Effect
Payload - The payload delivered when an effect completes.
- System
Effect - Built-in system effects that every platform executor must handle.