SlotFlow API Documentation

ScheduleRequest extends PlanRequest
in package

FinalYes

Immutable request for one planning-oriented schedule computation.

Tags
experimental

The timed and demand-scheduling layer is unproven against a real workload: tested and documented, but not yet validated by a production consumer, so its shape is expected to change once one exists. Pin an exact version if you build on it. The execution engine carries no such caveat.

Table of Contents

Properties

$flow  : Flow
$originTime  : int
$params  : array<string, string>
$quantity  : int|float
$space  : SlotSpace
$startTime  : int
$state  : QuantityState
$target  : Slot

Methods

__construct()  : mixed
Create one schedule-planning request.

Properties

$params read-only

public array<string, string> $params

Methods

__construct()

Create one schedule-planning request.

public __construct(QuantityState $state, SlotSpace $space, Flow|non-empty-string $flow, int|float $quantity, Slot|non-empty-string $target[, DateTimeImmutable|int|string $startTime = 0 ][, array<string, scalar|null> $params = [] ]) : mixed
Parameters
$state : QuantityState
$space : SlotSpace
$flow : Flow|non-empty-string
$quantity : int|float
$target : Slot|non-empty-string
$startTime : DateTimeImmutable|int|string = 0
$params : array<string, scalar|null> = []
On this page

Search results