(item: T, ctx: EffectContext<T, EEnqueue, R>): Effect.Effect<void, E, R>export type type QueueWorkerEffect<
T,
E,
EEnqueue = never,
R = never
> = (
item: T,
ctx: EffectContext<T, EEnqueue, R>
) => Effect.Effect<void, E, R>
function (type parameter) T in type QueueWorkerEffect<T, E, EEnqueue = never, R = never>T, function (type parameter) E in type QueueWorkerEffect<T, E, EEnqueue = never, R = never>E, function (type parameter) EEnqueue in type QueueWorkerEffect<T, E, EEnqueue = never, R = never>EEnqueue = never, function (type parameter) R in type QueueWorkerEffect<T, E, EEnqueue = never, R = never>R = never> = (
item: Titem: function (type parameter) T in type QueueWorkerEffect<T, E, EEnqueue = never, R = never>T,
ctx: EffectContext<T, EEnqueue, R>(parameter) ctx: {
add: QueueEnqueue<T, EEnqueue, R>;
prioritize: QueueEnqueue<T, EEnqueue, R>;
defer: QueueEnqueue<T, EEnqueue, R>;
attempts: number;
enqueuedAt: number;
priority: Priority;
}
interface EffectContext<T, EEnqueue = never, R = never>Context passed to the effect callback during item processing.
Provides guarded enqueue operations for spawning derived/follow-up work.
Attempting to enqueue the same item (by reference or by key) logs a warning
and silently drops the item to prevent infinite processing loops.
For intentional re-processing, fail the worker effect (auto re-enqueue applies up to
QueueHyperlinkConfigBase.attempts
) or re-inject via queue.enqueue off the events stream.
EffectContext<function (type parameter) T in type QueueWorkerEffect<T, E, EEnqueue = never, R = never>T, function (type parameter) EEnqueue in type QueueWorkerEffect<T, E, EEnqueue = never, R = never>EEnqueue, function (type parameter) R in type QueueWorkerEffect<T, E, EEnqueue = never, R = never>R>,
) => 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, function (type parameter) E in type QueueWorkerEffect<T, E, EEnqueue = never, R = never>E, function (type parameter) R in type QueueWorkerEffect<T, E, EEnqueue = never, R = never>R>;