A state machine abstraction for React
A state machine abstraction for React that provides declarative state management and automatic test generation.
> react and react-test-renderer are peer dependencies.
``sh`
yarn add react-automata
`js
// App.js
import React from 'react'
import { Action, withStateMachine } from 'react-automata'
const statechart = {
initial: 'a',
states: {
a: {
on: {
NEXT: 'b',
},
onEntry: 'sayHello',
},
b: {
on: {
NEXT: 'a',
},
onEntry: 'sayCiao',
},
},
}
class App extends React.Component {
handleClick = () => {
this.props.transition('NEXT')
}
render() {
return (
export default withStateMachine(statechart)(App)
`
`js
// App.spec.js
import { testStateMachine } from 'react-automata'
import App from './App'
test('it works', () => {
testStateMachine(App)
})
`
`js
// App.spec.js.snap
exports[it works: a 1] =
;exports[
it works: b 1] = ;
`API
withStateMachine(statechart[, options])(Component)
The
higher-order component accepts an xstate configuration object or an xstate machine, some options and a component.
It returns a new component with special props, action and activity methods and additional lifecycle hooks.
The initial machine state and the initial data can be passed to the resulting component through the initialMachineState and initialData props.$3
| Option | Type | Description |
| ------ | ---- | ----------- |
| channel | string | The key of the context on which to set the state. |
| devTools | bool | To connect the state machine to the Redux DevTools Extension. |
$3
#### transition(event[, updater])
The method to change the state of the state machine.
It takes an optional updater function that receives the previous data and returns a data change.
The updater can also be an object, which gets merged into the current data.
`js
handleClick = () => {
this.props.transition('FETCH')
}
`#### machineState
The current state of the state machine.
> It's not recommended to use this value because it couples the component and the state machine.
js
`$3
All the component's methods whose names match the names of actions and activities, are fired when the related transition happen.
Actions receive the state and the event as arguments. Activities receive a boolean that is true when the activity should start, and false otherwise.
For example:
js
const statechart = {
// ...
fetching: {
on: {
SUCCESS: 'success',
ERROR: 'error',
},
onEntry: 'fetchGists',
},
// ...
}class App extends React.Component {
// ...
fetchGists() {
fetch('https://api.github.com/users/gaearon/gists')
.then(response => response.json())
.then(gists => this.props.transition('SUCCESS', { gists }))
.catch(() => this.props.transition('ERROR'))
}
// ...
}
`$3
#### componentWillTransition(event)
The lifecycle method invoked when the transition function has been called.
It provides the event, and can be used to run side-effects.
js
componentWillTransition(event) {
if (event === 'FETCH') {
fetch('https://api.github.com/users/gaearon/gists')
.then(response => response.json())
.then(gists => this.props.transition('SUCCESS', { gists }))
.catch(() => this.props.transition('ERROR'))
}
}
`#### componentDidTransition(prevMachineState, event)
The lifecycle method invoked when a transition has happened and the state is updated.
It provides the previous state machine, and the event.
The current
is available in this.props.`js
componentDidTransition(prevMachineState, event) {
Logger.log(event)
}
`<Action />
The component to define which parts of the tree should be rendered for a given action (or set of actions).
| Prop | Type | Description |
| ---- | ---- | ----------- |
| is | oneOfType(string, arrayOf(string)) | The action(s) for which the children should be shown. It accepts the exact value, a glob expression or an array of values/expressions (e.g.
, is="show" or is={['fetch', 'show']). |
| channel | string | The key of the context from where to read the state. |
| children | node | The children to be rendered when the conditions match. |
| render | func | The render prop receives a bool (true when the conditions match) and it takes precedence over children. |
| onHide | func | The function invoked when the component becomes invisible. |
| onShow | func | The function invoked when the component becomes visible. |`js
Oh, snap!
`js
render={visible => (visible ? Oh, snap! : null)}
/>
`<State />
The component to define which parts of the tree should be rendered for a given state (or set of states).
| Prop | Type | Description |
| ---- | ---- | ----------- |
| is | oneOfType(string, arrayOf(string)) | The state(s) for which the children should be shown. It accepts the exact value, a glob expression or an array of values/expressions (e.g.
, is="error." or is={['idle', 'error.']). |
| channel | string | The key of the context from where to read the state. |
| children | node | The children to be rendered when the conditions match. |
| render | func | The render prop receives a bool (true when the conditions match) and it takes precedence over children. |
| onHide | func | The function invoked when the component becomes invisible. |
| onShow | func | The function invoked when the component becomes visible. |`js
Oh, snap!
`js
render={visible => (visible ? Oh, snap! : null)}
/>
`testStateMachine(Component[, { fixtures, extendedState }])
The method to automagically generate tests given a component wrapped into
.
It accepts an additional fixtures option to describe the data to be injected into the component for a given transition, and an extendedState option to control the statechart's conditions - both are optional.`js
const fixtures = {
initialData: {
gists: [],
},
fetching: {
SUCCESS: {
gists: [
{
id: 'ID1',
description: 'GIST1',
},
{
id: 'ID2',
description: 'GIST2',
},
],
},
},
}test('it works', () => {
testStateMachine(App, { fixtures })
})
``You might find the answer to your question here.
Federico, for telling me "Hey, I think building UIs using state machines is the future".
David, for giving an awesome talk about infinitely better UIs, and building xstate.
Ryan, for experimenting with xstate and React - Ryan's approach to React has always been a source of inspiration to me.
Erik, for writing about statecharts, and showing me how to keep UI and state machine decoupled.