(controls: ProcessScheduleControls): Effect.Effect<void, never, R>A function that seeds a process's schedule via its ProcessScheduleControls.
export type type ProcessScheduleInitializer<
R = never
> = (
controls: ProcessScheduleControls
) => Effect.Effect<void, never, R>
A function that seeds a process's schedule via its
ProcessScheduleControls
.
ProcessScheduleInitializer<function (type parameter) R in type ProcessScheduleInitializer<R = never>R = never> = (
controls: ProcessScheduleControls(parameter) controls: {
entries: Effect.Effect<ReadonlyArray<ProcessScheduleEntry>, never, never>;
set: (entries: ReadonlyArray<ProcessScheduleEntry>) => Effect.Effect<void, never, never>;
add: (entry: ProcessScheduleEntry) => Effect.Effect<void, never, never>;
clear: Effect.Effect<void, never, never>;
}
controls: ProcessScheduleControls,
) => import EffectEffect.interface Effect<out A, out E = never, out R = never>The Effect interface defines a value that lazily describes a workflow or
job. The workflow requires some context R, and may fail with an error of
type E, or succeed with a value of type A.
When to use
Use when you need to represent a lazy, composable workflow that can require
services, fail with a typed error, or succeed with a typed value.
Details
Effect values model resourceful interaction with the outside world,
including synchronous, asynchronous, concurrent, and parallel interaction.
They use a fiber-based concurrency model, with built-in support for
scheduling, fine-grained interruption, structured concurrency, and high
scalability.
To run an Effect value, you need a Runtime, which is a type that is
capable of executing Effect values.
Effect<void, never, function (type parameter) R in type ProcessScheduleInitializer<R = never>R>;