Download the PHP package konsulting/fluent-state-machine without Composer
On this page you can find all versions of the php package konsulting/fluent-state-machine. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package fluent-state-machine
Fluent State Machine
A simple fluent implementation of a state machine. If you've ever battled with trying to control and report state for an object in your php project - a state machine will help.
There are a few notable php state machine libraries around already - but didn't quite fit right, although we've used them in projects before. This is not an exhaustive list.
- yohang/finite
- winzou/state-machine
- definitely246/state-machine
- Symfony WorkFlow Component can be used as a State Machine.
Installation
composer require konsulting/state-machine
Simple Example
We can construct a basic state machine easily, using a door as an example:
When constructing a StateMachine, the first state is assumed to be the default.
We can then try to transition the state machine to a new state:
We can also check if a transition is possible:
Real usage
In real usage, we will have a object (model) where the state machine is responsible for controlling the transitions that can be applied (and therefore controlling the models behaviour)
This can be accomplished two ways with this library.
-
We can attach a model to the state machine, and the state machine can manipulate the model. In very simple cases, this may be enough.
- We can attach the state machine to a model, and the model's methods use the state machine to determine if it is able to proceed with an action.
Real usage 1 - attach a model to the state machine
As you will see, only the state machine retains the state information and we use it to control the flow in the script.
Side note: This example makes use of automatic wiring to use a model method called the same name as the transition (in camelCase). We can also define a method specifically by passing a string, or any other callable.
Real usage 2 - attach the state machine to a model
For this we extend the AttachableStateMachine which is set up to allow us to programmatically define the state machine, and accepts a model as its' constructor.
The end point is that we use the model in the natural manner we want to.
In the door class' methods we pass through a callback to be run as part of the transition. We are also able to pass through a callback to be run if the transition fails (instead of throwing an exception).
The AttachedStateMachine defines itself during construction. It grabs the current status from the model, and makes sure to stamp it back when setting the current status.
We also stop the auto wiring, so the state machine doesn't end up in an infinite loop trying to call it's calling method.
Contributing
Contributions are welcome and will be fully credited. We will accept contributions by Pull Request.
Please:
- Use the PSR-2 Coding Standard
- Add tests, if you’re not sure how, please ask.
- Document changes in behaviour, including readme.md.
Testing
We use PHPUnit
Run tests using PHPUnit: vendor/bin/phpunit
All versions of fluent-state-machine with dependencies
danielstjules/stringy Version ^3.1
symfony/event-dispatcher Version ^3.3 | ^4.0 | 5.0