A simple, yet powerful state machine framework for Dart supporting Flutter and web apps.
This library is open source, stable and well tested. Development happens on GitHub. Feel free to report issues or create a pull-request there. General questions are best asked on StackOverflow.
The package is hosted on dart packages. Up-to-date class documentation is created with every release.
Follow the installation instructions on dart packages.
Import the package into your Dart code using:
import 'package:statemachine/statemachine.dart';To create a new state machine instantiate Machine:
final machine = Machine<String>();The type of the state machine is used to uniquely identify states of the machine. In this simple example we use a String; but typically you would use an enum, a Symbol, or an arbitrary other identifying object.
To create states call Machine.newState and store them in variables. Each state needs an identifying key of the declared type, as described above we use a String that helps debugging.
final startState = machine.newState('start');
final activeState = machine.newState('active');By default, the first state created is also the start state of the machine. It is possible to explicitly create start and stop states of the machine using Machine.newStartState and Machine.newStopState.
States support callbacks whenever a state is entered or left.
someState.onEntry(() => print('activated'));
someState.onExit(() => print('deactivate'));To start a state machine and set its state to its starting state call Machine.start:
machine.start();Similarly, you can stop a machine by calling Machine.stop.
There are various ways in which your machine can switch states.
From anywhere within your code you can enter a specific state by calling State.enter.
someState.enter();Depending on context, it might be easier to set the current state using the accessor on the state machine itself:
machine.current = someState;Alternatively, you can also use the identifying object to set the active state:
machine.current = 'active';You can define transitions between states that are triggered by events using State.onStream. The example below registers for click events when the inactive state is entered. In case of a click event the callback is executed, and the state machine transitions into the new state:
someState.onStream(element.onClick, (value) => anotherState.enter());Also, transitions can be triggered by the completion of a future using State.onFuture. Since futures cannot be suspended or cancelled, the future continues to run even if the owning state is deactivated. Should the state be activated, and the future value is already present, then the value is immediately supplied into the callback. Further activations have no effect.
someState.onFuture(computation, (value) => anotherState.enter());Also, you can automatically trigger callbacks after a timeout using State.onTimeout. The following snippet calls the callback 1 second after the active state is entered and falls back to another state:
someState.onTimeout(Duration({seconds: 1}), () => anotherState.enter());Callbacks often contain code to check for additional constraints and update other objects or UI element before entering a different state. See the tooltip example directory for a more complete illustration of the functionality provided by this library.
Machines can be nested. Simply add another machine that gets started when the state is entered, and stopped when the state is left.
someState.addNested(anotherMachine);- The Rise Of The State Machines.
- You are managing state? Think twice.
- Robust React User Interfaces with Finite State Machines.
The MIT License, see LICENSE.