Prebuilt middlewares

The MST package ships with some prebuilt middlewares, which serves mainly as examples on how to write your own middleware. The source of each middleware can be found in this github directory, you are encouraged to read them!

The middlewares are bundled separately to keep the core package small, and can be included using:

import { MiddlewareName } from "mst-middlewares"

The middlewares serve as example and are supported on a best effort bases. The goal of these middlewares is that if they are critical to your system, you can simply copy paste them and further tailor them towards your specific needs.

For the exact description of all middleware events offered by MST, see the api docs

Contributing

Feel free to contribute to these middlewares and improve them on your experience. The middlewares must be written in TypeScript. Any additional test for your middleware should be written inside the test folder

simple-action-logger

This is the most basic of middlewares: It logs all direct action invocations. Example:

import { simpleActionLogger } from "mst-middlewares"

// .. type definitions ...

const store = Store.create({
    todos: [{ title: "test " }]
})

mst.addMiddleware(store, simpleActionLogger)

store.todos[0].setTitle("hello world")

// Prints:
// [MST] /todos/0/setTitle

For a more sophisticated logger, see action-logger which also logs process invocations and continuations

action-logger

This is a little more sophisticated middlewares: It logs all direct action invocations and also every flow that spawns, returns or throws. Example:

import { actionLogger } from "mst-middlewares"

// .. type definitions ...

const store = Store.create({
    todos: [{ title: "test " }]
})

mst.addMiddleware(store, actionLogger)

store.todos[0].setTitle("hello world")

This will print something like `[MST] -

[MST] #5 action - /todos/0/setTitle
[MST] #5 flow_spawn - /todos/0/setTitle
[MST] #5 flow_spawn - /todos/0/helper2
[MST] #5 flow_return - /todos/0/helper2
[MST] #5 flow_return - /todos/0/setTitle

The number ("#5") indicates the id of the original action invocation that lead directly or indirectly to the flow being spawned. For more details on the meaning of the action types see the middleware docs.

atomic

This middleware rolls back if a synchronous or asynchronous action process fails.

The exception itself is not eaten, but any modifications that are made during the sync/async action will be rollback, by reverse applying any pending patches. Can be connected to a model by using either addMiddleware or decorate

Example:

import { types, addMiddleware, flow } from "mobx-state-tree"
import { atomic } from "mst-middlewares"

const TestModel = types
    .model({
        z: 1
    })
    // example with addMiddleware
    .actions(self => {
        addMiddleware(self, atomic)

        return {
            inc: flow(function*(x) {
                yield delay(2)
                self.z += x
                yield delay(2)
                self.z += x
                throw "Oops"
            })
        }
    })
    // example with decorate
    .actions(self => {
        return {
            inc: decorate(
                atomic,
                flow(function*(x) {
                    yield delay(2)
                    self.z += x
                    yield delay(2)
                    self.z += x
                    throw "Oops"
                })
            )
        }
    })

const m = TestModel.create()
m.inc(3).catch(error => {
    t.is(error, "Oops")
    t.is(m.z, 1) // Not 7! The change was rolled back
})

TimeTraveller

This built in model can be used as stand alone store or as part of your state tree and adds time travelling capabilities. It records all emitted snapshots by a tree and exposes the following methods / views:

• canUndo: boolean
• canRedo: boolean
• undo()
• redo()
• history: array with all recorded states

The state of the TimeTraveller itself is stored in a Mobx state tree, meaning that you can freely snapshot your state including its history. This means that it is possible to store your app state including the undo stack in for example local storage. (but beware that stringify-ing will not benefit from structural sharing).

Usage inside a state tree:

import { TimeTraveller } from "mst-middleware"

export const Store = types.model({
    todos: types.array(Todo),
    history: types.optional(TimeTraveller, { targetPath: "../todos" })
})

const store = Store.create()

// later:
if (store.history.canUndo) store.history.undo()
// etc

Note that the targetPath is a path relative to the TimeTraveller instance that will indicate which part of the tree will be snapshotted. Please make sure the targetPath doesn't point to a parent of the time traveller, as that would start recording it's own history..... In other words, targetPath: "../" -> Boom💥

To instantiate the TimeTraveller as a stand-alone state tree, pass in the the store through context:

import { TimeTraveller } from "mst-middlewares"

export const Store = types.model({
    todos: types.array(Todo)
})

const store = Store.create()
const timeTraveller = TimeTraveller.create({}, { targetStore: store })

// later:
if (timeTraveller.canUndo) timeTraveller.undo()
// etc

UndoManager

The UndoManager is the more fine grained TimeTraveller. Because it records patches instead of snapshots, it is better at dealing with concurrent and asynchronous processes. The differences to the TimeTraveller make it useful to implement end-user undo / redo.

For an in-depth explanation why undo / redo should be patch, not snapshot, based, check out the second half of the React Next talk: MobX-state-tree, React but for data

Differences to the TimeTraveller:

1. It records patches for actions / processes, not snapshots. It's therefore using less memory.
2. undo / redo applies all inverted patches / patches for a recorded action / process instead of snapshots.
3. An undo state is only comitted to the history if the action / process is finished. Ongoing processes can't be undone.
4. Failing processes do not add an undo state.
5. Multiple concurrent processes only undo their own changes and don't touch the changes caused by other actions - unlike snapshots would.
6. Can be used declaratively within the models.

API:

• history: { patches: [], inversePatches [] }[]
• canUndo: boolean true if there is at least one undo level available
• canRedo: boolean true if there is at least one redo level available
• undoLevels: number number of undo levels available
• redoLevels: number number of redo levels available
• undo() undo the last operation
• redo() redo the last operation
• withoutUndo(() => fn) patches for actions / processes within the fn are not recorded.
• withoutUndoFlow(fn*) patches the fn* are not recorded.
• startGroup(() => fn) can be used to start a group, all patches within a group are saved as one history entry.
• stopGroup() can be used to stop the recording of patches for the grouped history entry.
• clear({ undo?: true, redo: true }?) clear the history.

Setup and API usage examples:

The setup is very similar to the one of the TimeTraveller. The UndoManager automatically records all the actions within the tree it is attached to.

If you want the history to be a part of your store:

import { UndoManager } from "mst-middlewares"

export const Store = types
    .model({
        todos: types.array(Todo),
        history: types.optional(UndoManager, {})
    })
    .actions(self => {
        // you could create your undoManger anywhere but before your first needed action within the undoManager
        setUndoManager(self)

        return {
            addTodo(todo) {
                self.todos.push(todo)
            }
            // to use the undoManager to wrap the afterCreate action
            // of the StoreModel it's necessary to set it within the store model like above
            // afterCreate: () => undoManager.withoutUndo(() => { action() })
        }
    })

export let undoManager = {}
export const setUndoManager = targetStore => {
    undoManager = targetStore.history
}
const store = Store.create()

To record the changes into a separate tree:

import { UndoManager } from "mst-middlewares"

export const Store = types
    .model({
        todos: types.array(Todo)
    })
    .actions(self => {
        // you could create your undoManger anywhere but before your first needed action within the undoManager
        setUndoManager(self)

        return {
            addTodo(todo) {
                self.todos.push(todo)
            }
            // to use the undoManager to wrap the afterCreate action
            // of the StoreModel it's necessary to set it within the store model like above
            // afterCreate: () => undoManager.withoutUndo(() => { action() })
        }
    })

export let undoManager = {}
export const setUndoManager = targetStore => {
    undoManager = UndoManager.create({}, { targetStore })
}
const store = Store.create()

Undo/ Redo:

import { undoManager } from "../Store"

// if the undoManger is created within another tree
const undo = () => undoManager.canUndo && undoManager.undo()
const redo = () => undoManager.canRedo && undoManager.redo()

WithoutUndo - within a react component:

import {undoManger} from '../Store'

...

setPersonName = () => {
    // the action setPersonName won't be saved onto the history, you could add more than one action.
    undoManger.withoutUndo(() => store.setPersonName('firstName', 'lastName'))
}

render() {
    return (
        <div onClick={this.setPersonName}>
            SetPersonName
        </div>
    )
}

...

WithoutUndo - declarative:

import { types } from "mobx-state-tree"
import { UndoManager } from "mst-middlewares"

const PersonModel = types
    .model("PersonModel", {
        firstName: types.string,
        lastName: types.string
    })
    .actions(self => {
        return {
            // setPersonName won't be recorded anymore in general
            setPersonName: (firstName, lastName) =>
                undoManager.withoutUndo(() => {
                    self.firstName = firstName
                    self.lastName = lastName
                })
        }
    })

const StoreModel = types
    .model("StoreModel", {
        persons: types.map(PersonModel)
    })
    .actions(self => {
        setUndoManager(self)

        return {
            addPerson(firstName, lastName) {
                persons.put({ firstName, lastName })
            }
        }
    })

export let undoManager = {}
export const setUndoManager = targetStore => {
    undoManager = UndoManager.create({}, { targetStore })
}
export const Store = StoreModel.create({})

WithoutUndoFlow - declarative:

import {undoManager} from './Store/'

...

.actions(self => {
    function updateBooks(json) {
        self.books.values().forEach(book => (book.isAvailable = false))
        json.forEach(bookJson => {
            self.books.put(bookJson)
            self.books.get(bookJson.id).isAvailable = true
        })
    }

    function* loadBooks() {
        try {
          const json = yield self.shop.fetch("/books.json")
          updateBooks(json)
        } catch (err) {
          console.error("Failed to load books ", err)
        }
    }

    return {
        loadBooks: () => undoManager.withoutUndoFlow(loadBooks)()
        // same as: undoManager.withoutUndo(() => flow(loadBooks))()
    }
})

StartGroup, StopGroup - within a react component:

import {undoManager} from '../Store'
...
handleStop = (mousePosition, { dx, dy }) => {
  this.stopTrackingDrag();
  undoManager.stopGroup();
}

handleDrag = (mousePosition, { dx, dy }) => {
  const { view, parentNode } = this.props;
  // only one history entry will be created for the whole dragging
  // therefore all patches will be merged to one history entry while the group is active
  undoManager.startGroup(() =>
    parentNode.moveSelectedNodes({ dx: dx / view.zoom, dy: dy / view.zoom })
  );
}
...

redux

The Redux 'middleware' is not literally middleware, but provides two useful methods for Redux interoperability:

asReduxStore

asReduxStore(mstStore, middlewares?) creates a tiny proxy around a MST tree that conforms to the redux store api. This makes it possible to use MST inside a redux application.

See the redux-todomvc example for more details.

connectReduxDevtools

connectReduxDevtools(remoteDevDependency, mstStore, options?) connects a MST tree to the Redux devtools. Pass in the remoteDev dependency to set up the connect (only one at a time). See this example for a setup example.

The options object is optional and has the following options:

• logIdempotentActionSteps: true by default due to possible performance penalty because of the internal usage of onPatch. When set to false it will skip reporting of actions and flow action "steps" that do not end up in an actual change in the model (except when an error is thrown), thus reducing the amount of noise in the logs.
• logChildActions: false by default. When set to true it will report actions that are executed inside a root actions. When set to false it will not.
• logArgsNearName: true by default. When true it will log the arguments near the action name (truncated if too long), when false it won't.