All Projects β†’ choojs β†’ Nanostate

choojs / Nanostate

Licence: apache-2.0
🚦- Small Finite State Machines

Programming Languages

javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to Nanostate

FiniteStateMachine
This project is a finite state machine designed to be used in games.
Stars: ✭ 45 (-70.2%)
Mutual labels:  fsm, state-machine, finite-state-machine
Finity
A finite state machine library for Node.js and the browser with a friendly configuration DSL.
Stars: ✭ 88 (-41.72%)
Mutual labels:  state-machine, finite-state-machine, fsm
xstate
State machines and statecharts for the modern web.
Stars: ✭ 21,286 (+13996.69%)
Mutual labels:  fsm, state-machine, finite-state-machine
use-state-machine
Use Finite State Machines with React Hooks
Stars: ✭ 28 (-81.46%)
Mutual labels:  fsm, state-machine, finite-state-machine
Django Fsm
Django friendly finite state machine support
Stars: ✭ 1,898 (+1156.95%)
Mutual labels:  state-machine, finite-state-machine, fsm
stateless
Finite State Machine porting from Stateless C#
Stars: ✭ 25 (-83.44%)
Mutual labels:  fsm, state-machine, finite-state-machine
pastafarian
A tiny event-based finite state machine
Stars: ✭ 20 (-86.75%)
Mutual labels:  fsm, state-machine, finite-state-machine
Fluent State Machine
Fluent API for creating state machines in C#
Stars: ✭ 195 (+29.14%)
Mutual labels:  state-machine, finite-state-machine, fsm
statemachine-go
🚦 Declarative Finite-State Machines in Go
Stars: ✭ 47 (-68.87%)
Mutual labels:  fsm, state-machine, finite-state-machine
UnityHFSM
A simple yet powerful class based hierarchical finite state machine for Unity3D
Stars: ✭ 243 (+60.93%)
Mutual labels:  fsm, state-machine, finite-state-machine
Jstate
Advanced state machines in Java.
Stars: ✭ 84 (-44.37%)
Mutual labels:  state-machine, finite-state-machine, fsm
Afsm
C++14 Finite State Machine library
Stars: ✭ 113 (-25.17%)
Mutual labels:  state-machine, finite-state-machine, fsm
simple-state-machine
A simple Java state machine for Spring Boot projects
Stars: ✭ 25 (-83.44%)
Mutual labels:  fsm, state-machine, finite-state-machine
Statecharts.github.io
There is no state but what we make. Feel free to pitch in.
Stars: ✭ 265 (+75.5%)
Mutual labels:  state-machine, finite-state-machine, fsm
Fsm As Promised
A finite state machine library using ES6 promises
Stars: ✭ 446 (+195.36%)
Mutual labels:  state-machine, finite-state-machine, fsm
Xstateful
A wrapper for xstate that stores state, handles transitions, emits events for state changes and actions/activities, and includes an optional reducer framework for updating state and invoking side-effects
Stars: ✭ 81 (-46.36%)
Mutual labels:  state-machine, finite-state-machine
Qpcpp
QP/C++ real-time embedded framework/RTOS for embedded systems based on active objects (actors) and hierarchical state machines
Stars: ✭ 124 (-17.88%)
Mutual labels:  state-machine, fsm
Hfsm2
High-Performance Hierarchical Finite State Machine Framework
Stars: ✭ 134 (-11.26%)
Mutual labels:  state-machine, fsm
Hal
πŸ”΄ A non-deterministic finite-state machine for Android & JVM that won't let you down
Stars: ✭ 63 (-58.28%)
Mutual labels:  state-machine, finite-state-machine
Fsm
Finite State Machine for Go
Stars: ✭ 1,269 (+740.4%)
Mutual labels:  finite-state-machine, fsm

nanostate

npm version build status downloads js-standard-style

Small Finite State Machines. Great data structure to make code more readable, maintainable and easier to debug.

Usage

var nanostate = require('nanostate')

var machine = nanostate('green', {
  green: { timer: 'yellow' },
  yellow: { timer: 'red' },
  red: { timer: 'green' }
})

machine.emit('timer')
console.log(machine.state)
// => 'yellow'

machine.emit('timer')
console.log(machine.state)
// => 'red'

machine.emit('timer')
console.log(machine.state)
// => 'green'

Hierarchical

Let's implement a traffic light that flashes red whenever there's a power outage. Instead of adding a powerOutage event to each normal state, we introduce a hierarchy which allows any normal state to emit the powerOutage event to change the state to flashingRed.

var nanostate = require('nanostate')

var machine = nanostate('green', {
  green: { timer: 'yellow' },
  yellow: { timer: 'red' },
  red: { timer: 'green' }
})

machine.event('powerOutage', nanostate('flashingRed', {
  flashingRed: { powerRestored: 'green' }
}))

machine.emit('timer')
console.log(machine.state)
// => 'yellow'

machine.emit('powerOutage')
console.log(machine.state)
// => 'flashingRed'

machine.emit('powerRestored')
console.log(machine.state)
// => 'green'

History (to be implemented)

Implementers note: keep track of the last state a machine was in before exiting to the next machine. That way if '$history' is called, it can be merged into the previous machine.

TODO: figure out how it works if machines are combined in a non-linear fashion.

var nanostate = require('nanostate')

var machine = nanostate('cash', {
  cash: { check: 'check' },
  check: { cash: 'cash' }
})

machine.join('next', nanostate('review', {
  review: { previous: '$history' }
}))

Parallel

Sometimes there's multiple parallel states that need expressing; nanostate.parallel helps with that. For example when editing text, a particular piece of text might be bold, italic and underlined at the same time. The trick is that all of these states operate in parallel

var nanostate = require('nanostate')

var machine = nanostate.parallel({
  bold: nanostate('off', {
    on: { 'toggle': 'off' },
    off: { 'toggle': 'on' },
  }),
  underline: nanostate('off', {
    on: { 'toggle': 'off' },
    off: { 'toggle': 'on' },
  }),
  italics: nanostate('off', {
    on: { 'toggle': 'off' },
    off: { 'toggle': 'on' },
  }),
  list: nanostate('none', {
    none: { bullets: 'bullets', numbers: 'numbers' },
    bullets: { none: 'none', numbers: 'numbers' },
    numbers: { bullets: 'bullets', none: 'none' }
  })
})

machine.emit('bold:toggle')
console.log(machine.state)
// => {
//   bold: 'on',
//   italics: 'off',
//   underline: 'off',
//   list: 'none'
// }

Nanocomponent

Usage in combination with nanocomponent to create stateful UI components.

var Nanocomponent = require('nanocomponent')
var nanostate = require('nanostate')

module.exports = class Component extends Nanocomponent {
  constructor (name, state, emit) {
    super(name, state, emit)

    this.state = {
      data: {},
      input: ''
    }

    this.machine = nanostate('idle', {
      idle: { click: 'loading' },
      loading: { resolve: 'data', reject: 'error' },
      data: { click: 'loading' },
      error: { click: 'loading' }
    })

    this.machine.on('loading', () => this.searchRepositories())
  }

  createElement () {
    var buttonText = {
      idle: 'Fetch Github',
      loading: 'Loading…',
      error: 'Github fail. Retry?',
      data: 'Fetch Again?'
    }[this.machine.state]

    return html`
      <div>
        <input
          type="text"
          value=${this.state.input}
          onChange=${e => (this.state.input = e.target.value) && this.rerender()}
        >
        <button
          onClick=${() => this.machine.emit('click')}
          disabled=${this.machine.state === 'loading'}
        >
          ${buttonText}
        </button>
        ${data && html`<div>${JSON.stringify(data, null, 2)}</div>`}
        ${this.machine.state === 'error' && html`<h1>Error</h1>`}
      </div>
    `
  }

  searchRepositories () {
    fetch(`${ROOT_URL}/${this.state.input}`)
      .then(res => res.json())
      .then(res => {
         this.state.data = res.data
         this.machine.emit('resolve')
       })
      .catch(err => this.machine.emit('reject'))
  }
}

API

machine = nanostate(initialState, transitions)

Create a new instance of Nanostate. Takes the name of the initial state, and a mapping of states and their corresponding transitions. A state mapping is defined as { 1: { 2: 3 }}, where 1 is the state's name, 2 is an event name it accepts, and 3 is the new state after the event has been emitted.

machine.emit(event)

Move from the current state to a new state. Will throw if an invalid command is passed.

machine.on(state, cb)

Trigger a callback when a certain state is entered. Useful to trigger side effects upon state change.

state = machine.state

Return the current state.

machine.event(eventName, machine) (to be implemented)

Add another machine to the transition graph. The first argument is an event name, which can be transitioned to from all other states in the graph.

machine = nanostate.parallel(machines) (to be implemented)

Combine several state machines into a single machine. Takes an object of state machines, where the key is used to prefix the events for the state machine.

Say we have two state machine: 'foo' and 'bar'. 'foo' has an event called 'beep'. When combined through .parallel(), the event on the combined machine would be 'foo:beep'.

Installation

$ npm install nanostate

See Also

License

Apache-2.0

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].