Download the PHP package league/pipeline without Composer
On this page you can find all versions of the php package league/pipeline. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
All versions of pipeline with dependencies
Informations about the package pipeline
This package provides a pipeline pattern implementation.
The pipeline pattern allows you to easily compose sequential stages by chaining stages.
In this particular implementation the interface consists of two parts:
A pipeline consists of zero, one, or multiple stages. A pipeline can process a payload. During the processing the payload will be passed to the first stage. From that moment on the resulting value is passed on from stage to stage.
In the simplest form, the execution chain can be represented as a foreach:
Effectively this is the same as:
Pipelines are implemented as immutable stage chains. When you pipe a new stage, a new pipeline will be created with the added stage. This makes pipelines easy to reuse, and minimizes side-effects.
Operations in a pipeline, stages, can be anything that satisfies the
type-hint. So closures and anything that's invokable is good.
Class based stages.
Class based stages are also possible. The StageInterface can be implemented which
ensures you have the correct method signature for the
Because the PipelineInterface is an extension of the StageInterface pipelines can be re-used as stages. This creates a highly composable model to create complex execution patterns while keeping the cognitive load low.
For example, if we'd want to compose a pipeline to process API calls, we'd create something along these lines:
Because pipelines themselves are immutable, pipeline builders are introduced to facilitate distributed composition of a pipeline.
The pipeline builders collect stages and allow you to create a pipeline at any given time.
This package is completely transparent when dealing with exceptions. In no case will this package catch an exception or silence an error. Exceptions should be dealt with on a per-case basis. Either inside a stage or at the time the pipeline processes a payload.