Table of Contents generated with DocToc
Protector Middlware
When you define synchronous actions in Twist, it's really important that they are actually synchronous. A common mistake is to do something asynchronous, like a network call, or setting a timeout. The problem with this, is that it makes the changes to the store in response to an action non-deterministic. If you're using the DevTools Middleware, this poses a particular problem, because it needs to be able to replay synchronous actions as you move forwards and backwards in time.
To help detect such common mistakes, Twist comes with protector middleware that automatically blocks certain common asynchronous operations from inside of synchronous action handlers - for example, setTimeout, setInterval, and the use of promises. If you need to do something asynchronous, just make the action asynchronous (@Action({async: true}))! Since this has to replace some of the browser globals to achieve this, we recommend only using the protector middleware in your development environment / builds - not for production builds.
To use this middleware, just pass it in when creating your store:
import { protectorMiddleware } from '@twist/core';
var store = new MyStore(INITIAL_STATE, [protectorMiddleware]);