StateMachine::addTransition() - Code Metrics - Inspection of "added link to amsterdam php meetup" - rolfvreijdenberger/izzum-statemachine - Measure and Improve Code Quality continuously with Scrutinizer

Completed
Push — master ( 50cef7...02ca20 )

by Rolf
created 2016-06-30 14:48 UTC
StateMachine::addTransition() D

↳ Parent: StateMachine
Complexity

Conditions	9
Paths	14
Size

Total Lines	37
Code Lines	18
Duplication

Lines	0
Ratio	0 %
Code Coverage

Tests	22
CRAP Score	9
Importance

Changes	12
Bugs	0	Features	1
Metric	Value
c	12
b	0
f	1
dl	0
loc	37
ccs	22
cts	22
cp	1
rs	4.909
cc	9
eloc	18
nc	14
nop	2
crap	9
<?php
namespace izzum\statemachine;
use izzum\statemachine\Context;
use izzum\statemachine\State;
use izzum\statemachine\Transition;
use izzum\statemachine\Exception;
use izzum\statemachine\utils\Utils;

/**
 * A statemachine is used to execute transitions from certain states to other
 * states, for an entity that represents a domain object, by applying guard logic 
 * to see if a transition is allowed and transition logic to process the transition.
 *
 *
 * PACKAGE PHILOSOPHY
 * This whole package strives to follow the open/closed principle, making it
 * open for extension (adding your own logic through subclassing) but closed
 * for modification. For that purpose, we provide Loader interfaces, Builders
 * and Persistence Adapters for the backend implementation. States and
 * Transitions can also be subclassed to store data and provide functionality.
 *
 * Following the same philosophy: if you want more functionality in the
 * statemachine, you can use the provided methods and override them in your
 * subclass. multiple hooks are provided. Most functionality should be provided by
 * using the diverse ways of interacting with the statemachine: callables can be injected,
 * commands can be injected, event handlers can be defined and hooks can be overriden.
 *
 * We have provided multiple persistance backends to function as a data store to store all
 * relevant information for a statemachine including configuration, transition history and current states.
 * - relational databases: postgresql, mysql, sqlite
 * - nosql key/value: redis
 * - nosql document based: mongodb 
 * Memory and session backend adapters can be used to temporarily store the state information.
 * yaml, json and xml loaders can be used to load configuration data from files containing those
 * data formats.
 * 
 * Examples are provided in the 'examples' folder and serve to highlight some of the
 * features and the way to work with the package. The unittests can serve as examples too, 
 * including interaction with databases.
 *
 *
 * ENVIRONMENTS OF USAGE:
 * - 1: a one time process:
 * -- on webpages where there are page refreshes in between (use session/pdo adapter)
 * see 'examples/session'
 * -- an api where succesive calls are made (use pdo adapter)
 * -- cron jobs (pdo adapter)
 * - 2: a longer running process:
 * -- a php daemon that runs as a background process (use memory adapter)
 * -- an interactive shell environment (use memory adapter)
 * see 'examples/interactive'
 * 
 * 
 * DESCRIPTION OF THE 4 MAIN MODELS OF USAGE:
 * - 1: DELEGATION: Use an existing domain model. You can use a subclass of the
 * AbstractFactory to get a StateMachine, since that will put the creation of
 * all the relevant Contextual classes and Transitions in a reusable model.
 * usage: This is the most formal, least invasive and powerful model of usage, but the most complex.
 * Use Rules and Commands to interact with your domain model without altering a domain model
 * to work with the statemachine.
 * see 'examples/trafficlight'
 * - 2: INHERITANCE: Subclass a statemachine. Build the full Context and all transitions in
 * the constructor of your subclass (which could be a domain model itself) and
 * call the parent constructor. use the hooks to provide functionality (optionally a ModelBuilder and callbacks).
 * usage: This is the most flexible model of usage, but mixes your domain logic with the statemachine.
 * see 'examples/inheritance'
 * - 3: COMPOSITION: Use object composition. Instantiate and build a statemachine in a domain
 * model and build the full Context, Transitions and statemachine there. Use a ModelBuilder and callbacks
 * to drive functionality.
 * usage: This is a good mixture between encapsulating statemachine logic and flexibility/formal usage. 
 * see 'examples/composition'
 * - 4: STANDALONE: Use the statemachine as is, without any domain models. Your application will use it and inspect the
 * statemachine to act on it. Use callables to provide functionality
 * usage: This is the easiest model of usage, but the least powerful.
 * see 'examples/interactive'
 *
 * MECHANISMS FOR GUARD AND TRANSITION LOGIC
 * 1. rules and commands: they are fully qualified class names of Rule and Command (sub)classes that can be injected
 *      in Transition and State instances. they accept the domain model provided via an EntityBuilder 
 *      in their constructor.
 * 2. hooks: the methods in this class that start with an underscore and can be overriden in a subclass.
 *      these can be used to provide a subclass of this machine specifically tailored to your application domain.
 *      @link http://c2.com/cgi/wiki?HookMethod
 * 3. eventHandlers: methods that can be defined on the domain model. They will only be called when they
 *      are defined on the domain model and all start with 'on' prefix eg: onExitState, onTransition
 *      @link: https://en.wikipedia.org/wiki/Event_(computing)#Event_handler
 * 4. callables: callables can be injected in Transition and State instances. callables are 
 *      user defined methods in various flavours (closure, instance methods, static methods etc.) that
 *      will be called if they are valid. This is the easiest way to start using the statemachine.
 *      @link https://php.net/manual/en/language.types.callable.php
 *      @see TransitionTest::shouldAcceptMultipleCallableTypes for all implementations
 *
 * DESCRIPTION OF FULL TRANSITION ALGORITHM (and the usage modes where they apply)
 * 1. guard: _onCheckCanTransition($transition) //hook: inheritance.
 * 2. guard: $entity->onCheckCanTransition($identifier, $transition) // event handler: delegation, composition, inheritance
 * 3. guard: $transition->can($context) // check Rule: delegation, composition, inheritance, standalone
 * 4. guard: $transition->can($context) // callable: standalone, delegation, composition, inheritance
 * !!!  If all (existing) guards return true, then the transition is allowed. return true/false to allow/disallow transition.
 * 5. logic: _onExitState($transition) //hook: inheritance
 * 6. logic: $entity->onExitState($identifier, $transition) //event handler: delegation, composition, inheritance
 * 7. logic: $state_from->exitAction($context) //execute Command: delegation, composition, inheritance, standalone
 * 8. logic: state exit: $callable($entity) // callable: standalone, delegation, composition, inheritance
 * 9. logic: _onTransition($transition) //hook: inheritance
 * 10. logic: $entity->onTransition($identifier, $transition) //event handler: delegation, composition, inheritance
 * 11. logic: $transition->process($context) //execute Command: delegation, composition, inheritance, standalone
 * 12. logic: $transition->process($context) // callable: standalone, delegation, composition, inheritance
 * 13. logic: $entity->onEnterState($identifier, $transition) //event handler: delegation, composition, inheritance
 * 14. logic: $state_to->entryAction($context) //execute Command: delegation, composition, inheritance, standalone
 * 15. logic: state entry: $callable($entity) // callable: standalone, delegation, composition, inheritance
 * 16. logic: _onEnterState($transition) //hook: inheritance
 *
 * each hook can be overriden and implemented in a subclass, providing
 * functionality that is specific to your application. This allows you to use
 * the core mechanisms of the izzum package and extend it to your needs.
 *
 *
 * each event handler might be implemented on the entity/domain object and will be called, only if
 * available, with the $transition and $event arguments.
 * 
 * each callable might be set on a transition or state and comes in different forms:
 * closure, anonymouse function, instance method, static methods etc. (see php manual)
 * 
 *  Each transition will take place only if the transition logic (Rule, hooks, event handlers &
 *  callables) allows it. Each exit state, transition and entry state will then execute specific logic
 * (Command, hooks, event handlers & callables).
 *
 * for simple applications, the use of callables and event handlers is advised since it
 * is easier to setup and use with existing code.
 *
 * for more formal applications, the use of rules and commands is advised since
 * it allows for better encapsulated (and tested) business logic and more flexibility in
 * configuration via a database or config file.
 * 
 * The statemachine should be loaded with States and Transitions, which define
 * from what state to what other state transitions are allowed. The transitions
 * are checked against guard clauses (in the form of a business Rule instance
 * and hooks, event handlers and callables) and transition logic (in the form of a Command
 * instance, hooks, event handlers and callables).
 *
 * Transitions can also trigger an exit action for the current state and an
 * entry action for the new state (also via Command instances, event handlers,hooks and
 * callables). This allows you to implement logic that is dependent on the
 * State and independent of the Transition.
 *
 * RULE/COMMAND logic
 * The Rule checks if the domain model (or it's derived data) applies and
 * therefore allows the transition, after which the Command is executed that can
 * actually alter data in the underlying domain models, call services etc.
 * Rules should have NO side effects, since their only function is to check if a 
 * Transition is allowed. Commands do the heavy lifting for executing logic that
 * relates to a transition.
 * 
 * EXCEPTIONS
 * All high level interactions that a client conducts with a statemachine
 * should expect exceptions since runtime exceptions could bubble up from the
 * application specific classes from your domain (eg: calling services, database interactions etc). 
 * Exceptions that bubble up from this statemachine are always izzum\statemachine\Exception types.
 *
 * NAMING CONVENTIONS
 * - A good naming convention for states is to use lowercase-hypen-seperated names:
 * new, waiting-for-input, starting-order-process, enter-cancel-flow, done
 * - A good naming convention for transitions is to bind the input and exit state
 * with the string '_to_', which is done automatically by this package eg: 
 * new_to_waiting-for-input, new_to_done so you're able to call $statemachine->transition('new_to_done');
 * - A good naming convention for events (transition trigger names) is to use
 * lowercase-underscore-seperated names (or singe words) so your able to call
 * $machine->start() or $machine->event_name() or $machine->handle('event_name') 
 * 
 * 
 * MISC
 * The implementation details of this machine make it that it can act both as
 * a mealy machine and as a moore machine. the concepts can be mixed and
 * matched.
 * 
 *
 * @author Rolf Vreijdenberger
 * @link https://en.wikipedia.org/wiki/Finite-state_machine
 * @link https://en.wikipedia.org/wiki/UML_state_machine
 */
class StateMachine {
    
    /**
     * The context instance that provides the context for the statemachine to
     * operate in.
     *
     * @var Context
     */
    private $context;
    
    /**
     * The available states.
     * these should be loaded via transitions
     * A hashmap where the key is the state name and the value is
     * the State.
     *
     * @var State[]
     */
    private $states = array();
    
    /**
     * The available transitions.
     * these should be loaded via the 'addTransition' method.
     * A hashmap where the key is the transition name and the value is
     * the Transition.
     *
     * @var Transition[]
     */
    private $transitions = array();
    
    /**
     * the current state
     *
     * @var State
     */
    private $state;
    
    // ######################## TRANSITION METHODS #############################
    

    /**
     * Constructor
     *
     * @param Context $context
     *            a fully configured context providing all the relevant
     *            parameters/dependencies to be able to run this statemachine for an entity.
     */
    public function __construct(Context $context)
    {
        // sets up bidirectional association
        $this->setContext($context);
    }

    /**
     * Apply a transition by name.
     *
     * this type of handling is found in moore machines.
     *
     * @param string $transition_name
     *            convention: <state-from>_to_<state-to>
     * @param string $message optional message. this can be used by the persistence adapter
     *          to be part of the transition history to provide extra information about the transition. 
     * @return boolean true if the transition was made
     * @throws Exception in case something went disastrously wrong or if the
     *         transition does not exist. An exception will lead to a (partially
     *         or fully) failed transition.
     * @link https://en.wikipedia.org/wiki/Moore_machine
     */
    public function transition($transition_name, $message = null)
    {
        $transition = $this->getTransitionWithNullCheck($transition_name);
        return $this->performTransition($transition, $message);
    }

    /**
     * Try to apply a transition from the current state by handling an event
     * string as a trigger.
     * If the event is applicable for a transition then that transition from the
     * current state will be applied.
     * If there are multiple transitions possible for the event, the transitions
     * will be tried until one of them is possible.
     *
     * This type of (event/trigger) handling is found in mealy machines.
     *
     * @param string $event
     *            in case the transition will be triggered by an event code
     *            (mealy machine)
     *            this will also match on the transition name
     *            (<state_to>_to_<state_from>)
     * @param string $message optional message. this can be used by the persistence adapter
     *          to be part of the transition history to provide extra information about the transition.  
     * @return bool true in case a transition was triggered by the event, false
     *         otherwise
     * @throws Exception in case something went horribly wrong
     * @link https://en.wikipedia.org/wiki/Mealy_machine
     * @link http://martinfowler.com/books/dsl.html for event handling
     *       statemachines
     */
    public function handle($event, $message = null)
    {
        $transitioned = false;
        $transitions = $this->getCurrentState()->getTransitionsTriggeredByEvent($event);
        foreach ($transitions as $transition) {
            $transitioned = $this->performTransition($transition, $message);
            if ($transitioned)
                break;
        }
        return $transitioned;
    }

    /**
     * Have the statemachine do the first possible transition.
     * The first possible transition is based on the configuration of
     * the guard logic and the current state of the statemachine.
     *
     * TRICKY: Be careful when using this function, since all guard logic must
     * be mutually exclusive! If not, you might end up performing the state
     * transition with priority n when you really want to perform transition
     * n+1.
     *
     * An alternative is to use the 'transition' method to target 1 transition
     * specifically:
     * $statemachine->transition('a_to_b');
     * So you are always sure that you are actually doing the intented
     * transition instead of relying on the configuration and guard logic (which
     * *might* not be correctly implemented, leading to transitions that would
     * normally not be executed).
     * 
     * @param string $message optional message. this can be used by the persistence adapter
     *          to be part of the transition history to provide extra information about the transition. 
     * @return boolean true if a transition was applied.
     * @throws Exception in case something went awfully wrong.
     *        
     */
    public function run($message = null)
    {
        try {
            $transitions = $this->getCurrentState()->getTransitions();
            foreach ($transitions as $transition) {
                $transitioned = $this->performTransition($transition, $message);
                if ($transitioned) {
                    return true;
                }
            }
        } catch(Exception $e) {
            // will be rethrown
            $this->handlePossibleNonStatemachineException($e, Exception::SM_RUN_FAILED);
        }
        // no transition done
        return false;
    }

    /**
     * run a statemachine until it cannot run any transition in the current
     * state or until it is in a final state.
     *
     * when using cyclic graphs, you could get into an infinite loop between
     * states. design your machine correctly.
     * @param string $message optional message. this can be used by the persistence adapter
     *          to be part of the transition history to provide extra information about the transition. 
     * @return int the number of sucessful transitions made.
     * @throws Exception in case something went badly wrong.
     */
    public function runToCompletion($message = null)
    {
        $transitions = 0;
        try {
            $run = true;
            while ( $run ) {
                // run the first transition possible
                $run = $this->run($message);
                if ($run) {
                    $transitions++;
                }
            }
        } catch(Exception $e) {
            $this->handlePossibleNonStatemachineException($e, $e->getCode());
        }
        return $transitions;
    }

    /**
     * Check if an existing transition on the curent state is allowed by the
     * guard logic.
     *
     * @param string $transition_name
     *            convention: <state-from>_to_<state-to>
     * @return boolean
     */
    public function canTransition($transition_name)
    {
        $transition = $this->getTransition($transition_name);
        return $transition === null ? false : $this->doCheckCanTransition($transition);
    }

    /**
     * checks if one or more transitions are possible and/or allowed for the
     * current state when triggered by an event
     *
     * @param string $event            
     * @return boolean false if no transitions possible or existing
     */
    public function canHandle($event)
    {
        $transitions = $this->getCurrentState()->getTransitionsTriggeredByEvent($event);
        foreach ($transitions as $transition) {
            if ($this->doCheckCanTransition($transition)) {
                return true;
            }
        }
        return false;
    }

    /**
     * check if the current state has one or more transitions that can be
     * triggered by an event
     *
     * @param string $event            
     * @return boolean
     */
    public function hasEvent($event)
    {
        $transitions = $this->getCurrentState()->getTransitionsTriggeredByEvent($event);
        if (count($transitions) > 0) {
            return true;
        }
        return false;
    }
    
    // ######################## CORE TRANSITION & TEMPLATE METHODS #############################
    

    /**
     * Perform a transition by specifiying the transitions' name from a state
     * that the transition is allowed to run.
     *
     * @param Transition $transition            
     * @param string $message optional message. this can be used by the persistence adapter
     *          to be part of the transition history to provide extra information about the transition.  
     * @return boolean true if the transition was succesful
     * @throws Exception in case something went horribly wrong
     * @link https://en.wikipedia.org/wiki/Template_method_pattern
     */
    private function performTransition(Transition $transition, $message = null)
    {
        // every method in this core routine has hook methods, event handlers and
        // callbacks it can call during the execution phase of the
        // transition steps if they are available on the domain model.
        try {
            
            if (!$this->doCheckCanTransition($transition)) {
                // one of the guards returned false or transition not found on current state.
                return false;
            }
            
            // state exit action: performed when exiting the state
            $this->doExitState($transition);
            // the transition is performed, with the associated logic
            $this->doTransition($transition, $message);
            // state entry action: performed when entering the state
            $this->doEnterState($transition);
        } catch(Exception $e) {
            $this->handlePossibleNonStatemachineException($e, Exception::SM_TRANSITION_FAILED, $transition);
        }
        return true;
    }

    /**
     * Template method to call a hook and to call a possible method
     * defined on the domain object/contextual entity
     *
     * @param Transition $transition            
     * @return boolean if false, the transition and its' associated logic will
     *         not take place
     * @throws Exception in case something went horribly wrong
     */
    private function doCheckCanTransition(Transition $transition)
    {
        try {
            // check if we have this transition on the current state.
            if (!$this->getCurrentState()->hasTransition($transition->getName())) {
                return false;
            }
            
            // possible hook so your application can place an extra guard on the
            // transition. possible entry~ or exit state type of checks can also
            // take place in this hook.
            if (!$this->_onCheckCanTransition($transition)) {
                return false;
            }
            // an event handler that is possibly defined on the domain model: onCheckCanTransition
            if (!$this->callEventHandler($this->getContext()->getEntity(), 'onCheckCanTransition', $this->getContext()->getIdentifier(), $transition)) {
                return false;
            }
            
            // this will check the guards defined for the transition: Rule and callable
            if (!$transition->can($this->getContext())) {
                return false;
            }
        } catch(Exception $e) {
            $this->handlePossibleNonStatemachineException($e, Exception::SM_CAN_FAILED);
        }
        // if we come here, this acts as a green light to start the transition.
        return true;
    }

    /**
     * the exit state action method
     *
     * @param Transition $transition            
     */
    private function doExitState(Transition $transition)
    {
        // hook for subclasses to implement
        $this->_onExitState($transition);
        // an event handler that is possibly defined on the domain model: onExitState
        $this->callEventHandler($this->getContext()->getEntity(), 'onExitState', $this->getContext()->getIdentifier(), $transition);
        // executes the command and callable associated with the state object
        $transition->getStateFrom()->exitAction($this->getContext());
    }

    /**
     * the transition action method
     *
     * @param Transition $transition            
     * @param string $message optional message. this can be used by the persistence adapter
     *          to be part of the transition history to provide extra information about the transition.          
     */
    private function doTransition(Transition $transition, $message = null)
    {
        // hook for subclasses to implement
        $this->_onTransition($transition);
        $entity = $this->getContext()->getEntity();
        $identifier = $this->getContext()->getIdentifier();
        // an event handler that is possibly defined on the domain model: onTransition
        $this->callEventHandler($entity, 'onTransition', $identifier, $transition);
        // executes the command and callable associated with the transition object
        $transition->process($this->getContext());
        
        // this actually sets the state so we are now in the new state
        $this->setState($transition->getStateTo(), $message);
    }

    /**
     * the enter state action method
     *
     * @param Transition $transition            
     */
    private function doEnterState(Transition $transition)
    {
        // an event handler that is possibly defined on the domain model: onEnterState
        $this->callEventHandler($this->getContext()->getEntity(), 'onEnterState', $this->getContext()->getIdentifier(), $transition);
        
        // executes the command and callable associated with the state object
        $transition->getStateTo()->entryAction($this->getContext());
        
        // hook for subclasses to implement
        $this->_onEnterState($transition);
    }
    
    // ######################## SUPPORTING METHODS #############################
    /**
     * All known/loaded states for this statemachine
     *
     * @return State[]
     */
    public function getStates()
    {
        return $this->states;
    }

    /**
     * get a state by name.
     *
     * @param string $name            
     * @return State or null if not found
     */
    public function getState($name)
    {
        return isset($this->states [$name]) ? $this->states [$name] : null;
    }

    /**
     * Add a state. without a transition.
     * Normally, you would not use this method directly but instead use
     * addTransition to add the transitions with the states in one go.
     * 
     * This method makes sense if you would want to load the statemachine with states
     * and not transitions, and then add the transitions with regex states.
     * This saves you the hassle of adding transitions before you add the
     * regex transitions (just so the states are already known on the machine).
     * 
     * in case a State is not used in a Transition, it will be orphaned and not 
     * reachable via other states.
     *
     * @param State $state 
     * @return boolean true if the state was not know to the machine or wasn't added, false otherwise.           
     */
    public function addState(State $state)
    {
        //no regex states
        if ($state->isRegex()) {
            return false;
        }
        //check for duplicates
        if (isset($this->states [$state->getName()])) {
            return false;
        }
        $this->states [$state->getName()] = $state;
        return true;
    }

    /**
     * sets the state as the current state and on the backend.
     * This should only be done:
     * - initially, right after a machine has been created, to set it in a
     * certain state if the state has not been persisted before.
     * - when changing context (since this resets the current state) via
     * $machine->setState($machine->getCurrentState())
     *
     * This method allows you to bypass the transition guards and the transition
     * logic. no exit/entry/transition logic will be performed
     *
     * @param State $state 
     * @param string $message optional message. this can be used by the persistence adapter
     *          to be part of the transition history to provide extra information about the transition.  
     * @throws Exception in case the state is not valid/known for this machine          
     */
    public function setState(State $state, $message = null)
    {
        
        if($this->getState($state->getName()) === null) {
            throw new Exception(sprintf("%s state '%s' not known to this machine", $this->toString(), $state->getName()), Exception::SM_UNKNOWN_STATE);
        }
        //get the state known to this machine so we are sure we have the correct reference
        //even if the client provides another instance of State with the same name
        $state = $this->getState($state->getName());
        $this->getContext()->setState($state->getName(), $message);
        $this->state = $state;
    }

    /**
     * add state information to the persistence layer if it is not there.
     * 
     * Used to mark the initial construction of a statemachine at a certain
     * point in time. This method only makes sense the first time a statemachine
     * is initialized and used since it will do nothing once a transition has been made.
     * 
     * It will set the initial state on the backend which sets
     * the construction time.
     * 
     * Make sure that the transitions and states are loaded before you call this method.
     * in other words: the machine should be ready to go.
     * 
     * @param string $message optional message. this can be used by the persistence adapter
     *          to provide extra information in the history of the machine transitions,
     *          in this case, about the first adding of this machine to the persistence layer. 
     * @return boolean true if not persisted before, false otherwise
     */
    public function add($message = null)
    {
        return $this->getContext()->add($this->getInitialState()->getName(), $message);
    }

    /**
     * gets the current state (or retrieve it from the backend if not set).
     *
     * the state will be:
     * - the state that was explicitely set via setState
     * - the state we have moved to after the last transition
     * - the initial state. if we haven't had a transition yet and no current
     * state has been set, the initial state will be retrieved (the state with State::TYPE_INITIAL)
     *
     * @return State
     * @throws Exception in case there is no valid current state found
     */
    public function getCurrentState()
    {
        // do we have a current state?
        if ($this->state) {
            return $this->state;
        }
        // retrieve state from the context if we do not find any state set.
        $state = $this->getState($this->getContext()->getState());
        if (!$state || $state == State::STATE_UNKNOWN) {
            // possible wrong configuration
            throw new Exception(sprintf("%s current state not found for state with name '%s'. %s", $this->toString(), $this->getContext()->getState(), 'are the transitions/states loaded and configured correctly?'), Exception::SM_NO_CURRENT_STATE_FOUND);
        }
        // state is found, set it and return
        $this->state = $state;
        return $this->state;
    }

    /**
     * Get the initial state, the only state with type State::TYPE_INITIAL
     *
     * This method can be used to 'add' the state information to the backend via
     * the context/persistence adapter when a machine has been initialized for
     * the first time.
     *
     * @param boolean $allow_null optional
     * @return State (or null or Exception, only when statemachine is improperly
     *         loaded)
     * @throws Exception if $allow_null is false an no inital state was found
     */
    public function getInitialState($allow_null = false)
    {
        $states = $this->getStates();
        foreach ($states as $state) {
            if ($state->isInitial()) {
                return $state;
            }
        }
        if ($allow_null) {
            return null;
        }
        throw new Exception(sprintf("%s no initial state found, bad configuration. %s", $this->toString(), 'are the transitions/states loaded and configured correctly?'), Exception::SM_NO_INITIAL_STATE_FOUND);
    }

    /**
     * All known/loaded transitions for this statemachine
     *
     * @return Transition[]
     */
    public function getTransitions()
    {
        return $this->transitions;
    }

    /**
     * get a transition by name.
     *
     * @param string $name
     *            convention: <state_from>_to_<state_to>
     * @return Transition or null if not found
     */
    public function getTransition($name)
    {
        return isset($this->transitions [$name]) ? $this->transitions [$name] : null;
    }

    /**
     * Add a fully configured transition to the machine.
     *
     * It is possible to add transition that have 'regex' states: states that
     * have a name in the format of 'regex:/<regex-here>/' or 'not-regex:/<regex-here>/'. 
     * When adding a transition with a regex state, it will be matched against all currently
     * known states if there is a match. If you just want to use regex transitions, 
     * it might be preferable to store some states via 'addState' first, so the 
     * 
     * Self transitions for regex states are disallowed by default
     * since you would probably only want to do that explicitly. Regex states
     * can be both the 'to' and the 'from' state of a transition.
     *
     * Transitions from a 'final' type of state are not allowed.
     *
     * the order in which transitions are added matters insofar that when a
     * StateMachine::run() is called, the first Transition for the current State
     * will be tried first.
     *
     * Since a transition has complete knowledge about it's states,
     * the addition of a transition will also trigger the adding of the
     * to and from state on this class.
     *
     * this method can also be used to add a Transition directly (instead of via
     * a loader). Make sure that transitions that share a common State use the same
     * instance of that State object and vice versa.
     *
     * @param Transition $transition  
     * @param boolean $allow_self_transition_by_regex optional: to allow regexes to set a self transition.
     * @return int a count of how many transitions were added. In case of a regex transition this might be
     *              multiple and in case a transition already exists it might be 0.
     */
    public function addTransition(Transition $transition, $allow_self_transition_by_regex = false)
    {
        $from = $transition->getStateFrom();
        $to = $transition->getStateTo();
        $all_states = $this->getStates();
        // check if we have regex states in the transition and get either the
        // original state back if it's not a regex, or all currently known
        // states that match the regex.
        $all_from = Utils::getAllRegexMatchingStates($from, $all_states);
        $all_to = Utils::getAllRegexMatchingStates($to, $all_states);
        $contains_regex = $from->isRegex() || $to->isRegex();
        $non_regex_transition = $transition;
        $count = 0;
        // loop trought all possible 'from' states
        foreach ($all_from as $from) {
            // loop through all possible 'to' states
            foreach ($all_to as $to) {
                if ($contains_regex && $from->getName() === $to->getName() && !$allow_self_transition_by_regex) {
                    // disallow self transition for regexes and from final states unless it is explicitely allowed.
                    continue;
                }
                if ($contains_regex) {
                    /*
                     * get a copy of the current transition that has a regex (so
                     * we have a non-regex state) and delegate to $transition to
                     * get that copy in case it's a subclass of transition and
                     * we need to copy specific fields
                     */
                    $non_regex_transition = $transition->getCopy($from, $to);
                }
                if ($this->addTransitionWithoutRegex($non_regex_transition)) {
                    $count++;
                }
            }
        }
        return $count;
    }

    /**
     * Add the transition, after it has previously been checked that is did not
     * contain states with a regex.
     *
     * @param Transition $transition   
     * @return boolean true in case it was added. false otherwise         
     */
    protected function addTransitionWithoutRegex(Transition $transition)
    {
        // don't allow transitions from a final state
        if ($transition->getStateFrom()->isFinal()) {
            return false;
        }
        
        // add the transition only if it already exists (no overwrites)
        if ($this->getTransition($transition->getName()) !== null) {
            return false;
        }
        $this->transitions [$transition->getName()] = $transition;
        
        $from = $transition->getStateFrom();
        // adds state only if it does not already exist (no overwrites)
        $this->addState($from);
        /* 
         * transitions create bidirectional references to the States
         * when they are made, but here the States that are set on the machine
         * can actually be different instances from different transitions (eg:
         * a->b and a->c => we now have two State instances of a)
         * we therefore need to merge the transitions on the existing states.
         * The LoaderArray class does this for us by default, but we do it here
         * too, just in case a client decides to call the 'addTransition' method
         * directly without a loader.
         */
        //get the state known to the machine, to prevent possible bug where client 
        //creates 2 different state instances with different configs. we won't know
        //how to resolve this anyway, so just pick the existing state (first in wins)
        $state = $this->getState($from->getName());
        // adds transition only if it does not already exist (no overwrites)
        $state->addTransition($transition);
        
        $to = $transition->getStateTo();
        // adds state only if it dooes not already exist (no overwrites)
        $this->addState($to);
        return true;
    }

    /**
     * Get the current context
     *
     * @return Context
     */
    public function getContext()
    {
        return $this->context;
    }

    /**
     * set the context on the statemachine and provide bidirectional
     * association.
     *
     * change the context for a statemachine that already has a context.
     * When the context is changed, but it is for the same statemachine (with
     * the same transitions), the statemachine can be used directly with the
     * new context.
     *
     * The current state is reset to whatever state the machine should be in
     * (either the initial state or the stored state) whenever a context change
     * is made.
     *
     * we can change context to:
     * - switch builders/persistence adapters at runtime
     * - reuse the statemachine for a different entity so we do not
     * have to load the statemachine with the same transition definitions
     *
     * @param Context $context            
     * @throws Exception
     */
    public function setContext(Context $context)
    {
        if ($this->getContext()) {
            // context already exists.
            if ($this->getContext()->getMachine() !== $context->getMachine()) {
                throw new Exception(sprintf("Trying to set context for a different machine. currently '%s' and new '%s'", $this->getContext()->getMachine(), $context->getMachine()), Exception::SM_CONTEXT_DIFFERENT_MACHINE);
            }
            
            // reset state TODO: move outside if statement
            $this->state = null;
        }
        $context->setStateMachine($this);
        $this->context = $context;
    }
    
    // #################### LOW LEVEL HELPER METHODS #########################
    

    /**
     * called whenever an exception occurs from inside 'performTransition()'
     * can be used for logging etc. in some sort of history structure in the persistence layer
     *
     * @param Transition $transition            
     * @param Exception $e            
     */
    protected function handleTransitionException(Transition $transition, Exception $e)
    {
        // override if necessary to log exceptions or to add some extra info
        // to the underlying storage facility (for example, an exception will
        // not lead to a transition, so this can be used to indicate a failed
        // transition in some sort of history structure)
        $this->getContext()->setFailedTransition($transition, $e);
    }

    /**
     * Always throws an izzum exception (converts a non-izzum exception to an
     * izzum exception)
     *
     * @param \Exception $e            
     * @param int $code
     *            if the exception is not of type Exception, wrap it and use
     *            this code.
     * @param Transition $transition
     *            optional. if set, we handle it as a transition exception too
     *            so it can be logged or handled
     * @throws Exception an izzum exception
     */
    protected function handlePossibleNonStatemachineException(\Exception $e, $code, $transition = null)
    {
        $e = Utils::wrapToStateMachineException($e, $code);
        if ($transition !== null) {
            $this->handleTransitionException($transition, $e);
        }
        throw $e;
    }

    /**
     * This method is used to trigger an event on the statemachine and
     * delegates the actuall call to the 'handle' method
     *
     * $statemachine->triggerAnEvent() actually calls
     * $this->handle('triggerAnEvent')
     *
     * This is also very useful if you use object composition to include a
     * statemachine in your domain model. The domain model itself can then use it's own
     * __call implementation to directly delegate to the statemachines' __call method.
     * $model->walk() will actually call $model->statemachine->walk() which will
     * then call $model->statemachine->handle('walk');
     *
     * since transition event names default to the transition name, it is
     * possible to execute this kind of code (if the state names contain allowed
     * characters):
     * $statemachine-><state_from>_to_<state_to>(); 
     * $statemachine->eventName();
     * $statemachine->eventName('this is an informational message about why we do this transition');
     *
     *
     * @param string $name
     *            the name of the unknown method called
     * @param array $arguments
     *            an array of arguments (if any).
     *            an argument could be $message (informational message for the transition)
     * @return bool true in case a transition was triggered by the event, false
     *         otherwise
     * @throws Exception in case the transition is not possible via the guard
     *         logic (Rule)
     * @link https://en.wikipedia.org/wiki/Object_composition
     */
    public function __call($name, $arguments)
    {
        //prepend the $name (event/trigger) to other arguments and call the 'handle' method
        array_unshift($arguments, $name);
        return call_user_func_array(array($this, 'handle'), $arguments);
    }

    /**
     * Helper method to generically call methods on the $object.
     * Try to call a method on the contextual entity / domain model ONLY IF the
     * method exists.Any arguments passed to this method will be passed on to the method
     * called on the entity.
     *
     * @param mixed $object
     *            the object on which we want to call the method
     * @param string $method
     *            the method to call on the object
     * @return boolean|mixed
     */
    protected function callEventHandler($object, $method)
    {
        // return true by default (because of transition guard callbacks that
        // might not exist)
        $output = true;
        // check if method exists.
        if (method_exists($object, $method)) { // && $object !== $this) { //prevent recursion

            $args = func_get_args();
            // remove $object and $method from $args so we only have the other arguments
            array_shift($args);
            array_shift($args);
            // have the methods be able to return what they like
            // but make sure the 'onCheckCanTransition method returns a boolean
            $output = call_user_func_array(array($object,$method), $args);
        }
        return $output;
    }

    /**
     * Helper method that gets the Transition object from a transition name or
     * throws an exception.
     *
     * @param string $name
     *            convention: <state_from>_to_<state_to>
     * @return Transition
     * @throws Exception
     */
    private function getTransitionWithNullCheck($name)
    {
        $transition = $this->getTransition($name);
        if ($transition === null) {
            throw new Exception(sprintf("transition not found for '%s'", $name), Exception::SM_NO_TRANSITION_FOUND);
        }
        return $transition;
    }

    public function toString($elaborate = false)
    {
        $output = get_class($this) . ": [" . $this->getContext()->getId(true) . "]";
        if (!$elaborate) {
            return $output;
        } else {
            $output . ' transitions: ' . count($this->getTransitions()) . ', states: ' . count($this->getStates()) . '.';
            $output .= '[transitions]: ' . implode(",", $this->getTransitions());
            $output .= '. [states]: ' . implode(",", $this->getStates()) . '.';
            return $output;
        }
    }

    public function __toString()
    {
        return $this->toString(true);
    }
    
    // ###################### HOOK METHODS #######################
    

    /**
     * hook method.
     * override in subclass if necessary.
     * Before a transition is checked to be possible, you can add domain
     * specific logic here by overriding this method in a subclass.
     * In an overriden implementation of this method you can stop the transition
     * by returning false from this method.
     *
     * @param Transition $transition            
     * @return boolean if false, the transition and it's associated logic will
     *         not take place
     */
    protected function _onCheckCanTransition(Transition $transition)

    {
        // eg: dispatch an event and see if it is rejected by a listener
        return true;
    }

    /**
     * hook method.
     * override in subclass if necessary.
     * Called before each transition will run and execute the associated
     * transition logic.
     * A hook to implement in subclasses if necessary, to do stuff such as
     * dispatching events, locking an entity, logging, begin transaction via
     * persistence
     * layer etc.
     *
     * @param Transition $transition            
     */
    protected function _onExitState(Transition $transition)

    {}

    /**
     * hook method.
     * override in subclass if necessary.
     *
     * @param Transition $transition            
     */
    protected function _onTransition(Transition $transition)

    {}

    /**
     * hook method.
     * override in subclass if necessary.
     * Called after each transition has run and has executed the associated
     * transition logic.
     * a hook to implement in subclasses if necessary, to do stuff such as
     * dispatching events, unlocking an entity, logging, cleanup, commit
     * transaction via
     * the persistence layer etc.
     *
     * @param Transition $transition            
     */
    protected function _onEnterState(Transition $transition)

    {}
}
rolfvreijdenberger / izzum-statemachine

GitHub Access Token became invalid

Push — master ( 50cef7...02ca20 )

StateMachine::addTransition() D

Complexity

Size

Duplication

Code Coverage

Importance

Duplication Side-by-Side

Filter issues like
