Repository navigation
Packvium 1.7.0
The reference validator ships in the package, quality looks ahead in its block solver, and a
request built from objects is refused as its JSON would be. No request or result field changes.
Added
Packvium\Validation\validate(array $request, array $result), withResultIssue(code,
detail) andMalformedResult(anInvalidArgumentExceptioncarryingkind). The reference
validator over the decoded JSON documents, returning an empty list for a valid result; it is
loaded like thePackvium\Commercefunctions and shares no code with the engine it checks. A
document integer past 64 bits is refused rather than judged. Available on PHP 7.3+ through
src-legacy/as well.StopAccessibilityConstraint::directionsFor(), whichConstraintActivitynow asks instead
of reading the configured doors.
Changed
- A request built from objects is refused as JSON is. A model constructor that
refuses a value throwsInvalidRequestException(code, reason, field""), a subclass of the
InvalidArgumentExceptionit threw before.Packer::pack()checks the objects with the JSON
rules before solving.FixedPlacementwith acontainerInstancebelow 1 is now refused by
pack()asinvalid_fixed_placement, not by its constructor. - Every schema enum value is refused as
not_allowed. A value outside its list in
allowed_rotations, the output and dimensional-weight units,shape_type,
ground_contact_ruleorconfiguration.solversisinvalid_requestwith reasonnot_allowed
at its JSON Pointer.ticksas an output unit is now refused; the schema never listed it. qualitylooks ahead in the block solver. Each round completes its leading
blocks greedily and commits the best, so the answer is never worse than the greedy pass. On
our 22 pinned benchmark requests every answer improved, at 3% more CPU. Under a tight effort
budget the block start can now reporttruncated/effort_limit.fastandbalancedare
unchanged.- A
nesting_heightnot below the item's height is refused asinvalid_valueat its
pointer, and with nooutputblock the result is written inunits.length's schema code.
Fixed
- The load rules walk a stack iteratively, and the dependency-cycle check no longer recurses.
- The covered ground-contact rule counts only supporters with positive area, so an item no
longer rests on a box it touches only at an edge. - A quantity past 2^53 − 1 on the object path is refused instead of exhausting memory.
- A route violation names its violators in sorted order.