norotaro/enumata

State machines for Eloquent models with Enums

v1.1.1 2023-08-18 12:29 UTC

Requires

• php: ^8.1
• illuminate/support: ^9.0|^10.0
• javoscript/laravel-macroable-models: ^1.0

Requires (Dev)

• laravel/pint: ^1.10
• mockery/mockery: ^1.6
• orchestra/testbench: ^8.5
• pestphp/pest: ^2.9
• phpstan/phpstan: ^1.10

MIT

• Nelson Otazo

• laravel
• eloquent
• state machines
• finite-state machines
• finite automaton
• finite automata

README

State Machines for Eloquent models using Enums.

Table of Contents

• Description
• Live demo
• Installation
• Basic usage
  • The State Definition file - enum file
  • Configuring the model
• Access the current state
• Transitioning
  • Disable default transition methods
  • Transition not allowed exception
  • Force transitions
• Nullable States
  • Create a State Definition file
  • Register the State Definition file
• The State Machine
  • Using the State Machine
    • Transitioning
    • Checking available transitions
• Events
  • Listening to events using $dispatchesEvents
  • Listening to events using Closures
• Testing
• Inspiration
• LICENSE

Description

This package helps to implement State Machines to Eloquent models in an easy way using Enum files to represent all possible states and also to configure transitions.

Live demo

You can check the norotaro/enumata-demo repository or go to the live version of the demo in this PHP Sandbox.

Installation

composer require norotaro/enumata

Basic usage

Having a model with a status field and 4 possible states:

$order->status; // 'pending', 'approved', 'declined' or 'processed'

We need to create an enum file with the State Definitions which we will call OrderStatus. We can do this with the make:model-state command:

php artisan make:model-state OrderStatus

The State Definition file - enum file

The above command will create a default file that we can adapt to meet our needs:

namespace App\Models;

use Norotaro\Enumata\Contracts\Nullable;
use Norotaro\Enumata\Contracts\DefineStates;

enum OrderStatus implements DefineStates
{
    case Pending;
    case Approved;
    case Declined;
    case Processed;

    public function transitions(): array
    {
        return match ($this) {
            // when the order is Pending we can approve() or decline() it
            self::Pending => [
                'approve' => self::Approved,
                'decline' => self::Delined,
            ],
            // when the order is Approved we can apply the processOrder() transition
            self::Approved => [
                'processOrder' => self::Processed,
            ],
        };
    }

    public static function default(): self
    {
        return self::Pending;
    }
}

The transitions() method must return an array with key=>value where the key is the name of the transition and the value is the state to apply in that transition.

Note that, by default, methods will be created in the model for each transition. In the case of the example, the approve(), decline(), and processOrder() methods will be created.

Configuring the model

In the model we have to register the HasStateMachines trait and then the enum file in the $casts property:

use Norotaro\Enumata\Traits\HasStateMachines;

class Order extends Model
{
    use HasStateMachines;

    protected $casts = [
        'status' => OrderStatus::class,
    ];
}

That's it! Now we can transition between the states.

Access the current state

If you access the attributes, Eloquent will return the enum object with the current state:

$model = new Order;
$model->save();

$model->status; // App\Model\OrderStatus{name: "Pending"}
$model->fulfillment; // null

Transitioning

By default this package will create methods in the model for each transition returned by transitions() so, for this example, we will have these methods available:

$model->approve(); // Change status to OrderStatus::Approved
$model->decline(); // Change status to OrderStatus::Declined
$model->processOrder(); // Change status to OrderStatus::Processed

Disable default transition methods

You can disable the creation of transition methods by making the $defaultTransitionMethods attribute of the model false.

Internally these methods use the transitionTo($state) method available in the StateMachine class, so you can implement your custom transition methods with it.

class Order extends Model
{
    use HasStateMachines;

    // disable the creation of transition methods
    public bool $defaultTransitionMethods = false;

    protected $casts = [
        'status' => OrderStatus::class,
    ];

    // custom transition method
    public function myApproveTransition(): void {
        $this->status()->transitionTo(OrderStatus::Approved);
        //...
    }
}

Transition not allowed exception

If a transition is applied and the current state does not allow it, the TransitionNotAllowedException will be thrown.

$model->status; // App\Model\OrderStatus{name: "Pending"}
$model->processOrder(); // throws Norotaro\Enumata\Exceptions\TransitionNotAllowedException

Force transitions

All the methods of transitions created by the trait and also the transitionTo() method have the force parameter which, when true, the transition is applied without checking the defined rules.

$model->status; // App\Model\OrderStatus{name: "Pending"}

$model->processOrder(force: true); // this will apply the transition and will not throw the exception

$model->status; // App\Model\OrderStatus{name: "Processed"}

$model->status()->transitionTo(OrderStatus::Pending, force:true); // will apply the transition without errors

Nullable States

If the model has nullable states we only have to implement the Norotaro\Enumata\Contracts\Nullable contract in the State Definition file.

As an example, we will add the fulfillment attribute to the Order model:

$order->fulfillment; // null, 'pending', 'completed'

Create a State Definition file

We can create the enum file with the make:model-state command and the --nullable option:

php artisan make:model-state OrderFulfillment --nullable

After editing the generated file we can have something like this:

namespace App\Models;

use Norotaro\Enumata\Contracts\Nullable;
use Norotaro\Enumata\Contracts\DefineStates;

enum OrderFulfillment implements DefineStates, Nullable
{
    case Pending;
    case Completed;

    public function transitions(): array
    {
        return match ($this) {
            self::Pending => [
                'completeFulfillment' => self::Completed,
            ],
        };
    }

    public static function default(): ?self
    {
        return null;
    }

    public static function initialTransitions(): array
    {
        return [
            'initFulfillment' => self::Pending,
        ];
    }
}

The initialTransitions() method must return the list of available transitions when the field is null.

As with transitions(), by default methods will be created with the name of the keys returned by initialTransitions().

Register the State Definition file

As we previously did with the status definition, we need to register the file in the $casts property:

use Norotaro\Enumata\Traits\HasStateMachines;

class Order extends Model
{
    use HasStateMachines;

    protected $casts = [
        'status'      => OrderStatus::class,
        'fulfillment' => OrderFulfillment::class,
    ];
}

The State Machine

To access the State Machine we only need to add parentheses to the attribute name:

$model->status(); // Norotaro\Enumata\StateMachine

If the attribute uses underscore such as my_attribute, you can access the state machine using my_attribute() or myAttribute().

Using the State Machine

Transitioning

We can transition between states with the transitionTo($state) method:

$model->status()->transitionTo(OrderStatus::Approved);

Checking available transitions

$model->status; // App\Model\OrderStatus{name: "Pending"}

$model->status()->canBe(OrderStatus::Approved); // true
$model->status()->canBe(OrderStatus::Processed); // false

Events

This package adds two new events to those dispatched by Eloquent by default and can be used in the same way.

More information about Eloquent Events can be found in the official documentation.

• transitioning:{attribute}: This event is dispatched before saving the transition to a new state.
• transitioned:{attribute}: This event is dispatched after saving the transition to a new state.

In the transitioning event you can access the original and the new state in this way:

$from = $order->getOriginal('fulfillment'); // App\Model\OrderFulfillment{name: "Pending"}
$to   = $order->fulfillment; // App\Model\OrderFulfillment{name: "Complete"}

Listening to events using $dispatchesEvents

use App\Events\TransitionedOrderFulfillment;
use App\Events\TransitioningOrderStatus;
use Norotaro\Enumata\Traits\HasStateMachines;

class Order extends Model
{
    use HasStateMachines;

    protected $casts = [
        'status'      => OrderStatus::class,
        'fulfillment' => OrderFulfillment::class,
    ];

    protected $dispatchesEvents = [
        'transitioning:status'     => TransitioningOrderStatus::class,
        'transitioned:fulfillment' => TransitionedOrderFulfillment::class,
    ];
}

Listening to events using Closures

The transitioning($field, $callback) and transitioned($field, $callback) methods help to register closures.

Note that the first parameter must be the name of the field we want to listen to.

use Norotaro\Enumata\Traits\HasStateMachines;

class Order extends Model
{
    use HasStateMachines;

    protected $casts = [
        'status'      => OrderStatus::class,
        'fulfillment' => OrderFulfillment::class,
    ];

    protected static function booted(): void
    {
        static::transitioning('fulfillment', function (Order $order) {
            $from = $order->getOriginal('fulfillment');
            $to   = $order->fulfillment;

            \Log::debug('Transitioning fulfillment field', [
                'from' => $from->name,
                'to' => $to->name,
            ]);
        });

        static::transitioned('status', function (Order $order) {
            \Log::debug('Order status transitioned to ' . $order->status->name);
        });
    }
}

Testing

To run the test suite:

composer run test

Inspiration

This package was inspired by asantibanez/laravel-eloquent-state-machines.

LICENSE

The MIT License (MIT). Please see License File for more information.