finity
finity copied to clipboard
A finite state machine library for Node.js and the browser with a friendly configuration DSL.
## The devDependency [webpack](https://github.com/webpack/webpack) was updated from `4.26.1` to `4.27.0`. π¨ [View failing branch](https://github.com/nickuraltsev/finity/compare/master...nickuraltsev:greenkeeper%2Fwebpack-4.27.0). This version is **covered** by your **current version range** and after updating it in your project...
I have to build a map of State machines and in case the node server goes down, I need to resurrect them all later in the exact states they were...
```js const worker = Finity .configure() .initialState('ready') .on('task_submitted').transitionTo('running') .state('running') // here I have the context.eventPayload // but if I want to inside the worker gerate a data to use in...
I'm using finity with react and I need to stop the FSM when a component will be unmounted. I figured a few ways to call the internal stop() method but...
## Version **0.3.0** of [shx](https://github.com/shelljs/shx) was just published. Dependency shx Current Version 0.2.2 Type devDependency The version **0.3.0** is **not covered** by your **current version range**. If you donβt accept...
## Version **3.0.0** of **gzip-size-cli** was just published. Dependency gzip-size-cli Current Version 2.1.0 Type devDependency The version **3.0.0** is **not covered** by your **current version range**. If you donβt accept...
TL;DR: I switched the `Object.create(null)` objects used to keep track of state and event configs with `new Map()`, and made sure no assumptions are made regarding what objects get fed...
My head is killing me, so I'ma leave this pretty bare right now. I added comments to the commits to explain a bit. Lemme know what you think; I can...