Behold. A plugin for Reactotron for working with mobx-state-tree.
This is a plugin for Reactotron, so you'll need either reactotron-react-native or reactotron-react-dom installed first.
This is also a plugin for mobx-state-tree, so you'll also need that installed as well.
In your app, add a dev-dependency to reactotron-mst.
yarn add reactotron-mst --save-devor
npm i reactotron-mst --save-devTo make Reactotron aware of this plugin, go to the file you are configuring reactotron currently and add this:
// import the plugin
import { mst } from "reactotron-mst"
// tell Reactotron to use this plugin
Reactotron.use(mst())This will bestow Reactotron the power to track mobx-state-tree nodes.
Finally, you need to give reactotron-mst your root tree node.
Here's an example of that in action:
// bring in Reactotron
import * as Reactotron from "reactotron-react-native"
// bring in your mst model
import { MyModel } from "./my-model"
// create an instance of your model
const myTree = MyModel.create()
// let reactotron-mst know about it
Reactotron.trackMstNode(myTree)When you use() the reactotron-mst, you can also pass options.
The filter property provides a way to control what is sent to Reactotron. It is a function which takes an IMiddlewareEvent and returns a boolean. If you return true, the message will be sent to the Reactotron app. false will ignore this message.
Here's an example which will stop all postProcessSnapshot-based actions from jumping the wire.
import Tron from "reactotron-react-native"
import { mst } from "reactotron-mst"
const RX = /postProcessSnapshot/
const filter = event => RX.test(event.name) === false
Tron.use(mst({ filter }))The default value for filter if you don't provide it is () => true, which means everything gets passed to Reactotron.
The queryMode property provides a way to switch between subscribing to live state or snapshots. The only time you'll want to subscribe to snapshots instead of live state is when verifying transitory state (via postProcessSnapshot) is not persisted.
The trackMstNode() function will only be available after you setup the reactotron-mst plugin. Make sure you do the previous setup step first or you'll see an error that says, trackMstNode is not a function.
This plugin hooks into Reactotron just like the redux one. So the basics are in place, but it'll be a much nicer experience once we start introducing some custom views specifically for mobx-state-tree. Consider this plugin's status: phase 1 right now. 😅
Unlike redux, mobx-state-tree doesn't have to have a single root node. I personally find it easier to set it up like this, though.
Currently, reactotron-mst only supports tracking 1 tree. Multi-tree support is planned, but requires a bit of retooling of the Reactotron app to support multiple states.
As a short-term hack, we might be able to find a way to do this by using a prefix to identify which tree you intend to work with. For example, if you would like to subscribe to a piece of state in a different tree, perhaps we could do something like this: $tree3.currentUser.password.
Synchronous actions work well, however there's some issues with async actions when using the mobx-state-tree flow() function. We're going to have to introduce a new UI view similar to redux-saga to display this. In the meantime, the action which kicks off the flow will be logged immediate and the return value will be untracked (for now... sorry!).