mobservable
Makes data observable. And functions reactive. Whut? Like Excel.
![mobservable channel on slack](https://img.shields.io/badge/slack-mobservable-blue.svg)
New to Mobservable? Take the [five minute, interactive introduction](https://mweststrate.github.io/mobservable/getting-started.html)
Introduction
Mobservable enables your data structures to become observable.
Next to that it can make your functions reactive, so that they re-evaluate whenever relevant data is altered. This has major benefits for the simplicity, maintainability and performance of your code. This is the promise of Mobservable:
- Write complex applications which unmatched simple code.
- Enable unobtrusive state management: be free to use mutable objects, cyclic references, classes and real references to store state.
- Write declarative views that track their own dependencies. No subscriptions, cursors or other redundant declarations to manage.
- Build high performing React applications without Flux or Immutable data structures.
- Predictable behavior: all views are updated synchronously and atomically.
The essentials
Mobservable can be summarized in two functions that will fundamentally simplify the way you write React applications.
Let's start by building a really really simple timer application:
var timerData = mobservable.observable({
secondsPassed: 0
});
setInterval(function() {
timerData.secondsPassed++;
}, 1000);
var Timer = mobservable.observer(React.createClass({
render: function() {
return (<span>Seconds passed: { this.props.timerData.secondsPassed } </span> )
}
}));
React.render(<Timer timerData={timerData} />, document.body);
So what will this app do? It does nothing! The timer increases every second, but the will UI never update. To fix that, we should force the UI to refresh somehow upon each interval.
But that is the kind of dependency we should avoid in our code. We shouldn't have to pull data from our state to update the UI. Instead, the data structures should be in control and call the UI when it needs an update. The state should be pushed throughout our application. This is called inversion of control.
We can apply two simple functions of Mobservable to achieve this.
mobservable.observable
The first function is observable
. It is the swiss knife of mobservable and turns any data structure and function into its reactive counterpart. Objects, arrays, functions; they can all be made reactive. Reactiveness is contagious; new data that is put in reactive data will become reactive as well. To make our timer reactive, just change the first three lines of the code:
var timerData = mobservable.observable({
secondsPassed: 0
});
mobservableReact.observer
The second important function is observer
from the mobservable-react
package. It turns a Reactjs component into a reactive one, that responds automatically to changes in data that is used by its render method. It can be used to wrap any react component, either created by using ES6 classes or createClass
. So to fix the example, just update the timer definition to:
var Timer = mobservableReact.observer(React.createClass{
}));
Its as simple as that. The Timer
will now automatically update each time timerData.secondsPassed
is altered.
The actual interesting thing about these changes are the things that are not in the code:
- The
setInterval
method didn't alter. It still treats timerData
as a plain JS object. - There is no state. Timer is still a dumb component.
- There is no magic context being passed through components.
- There are no subscriptions of any kind that need to be managed.
- There is no higher order component that needs configuration; no scopes, lenses or cursors.
- There is no forced UI update in our 'controller'.
- If the
Timer
component would be somewhere deep in our app; only the Timer
would be re-rendered. Nothing else.
All this missing code... it will scale well into large code-bases!
It does not only work for plain objects, but also for arrays, functions, classes, deeply nested structures.
Getting started
Resources
Examples
Philosophy
Mobservable is inspired by Microsoft Excel and existing TFRP implementations like MeteorJS tracker, knockout and Vue.js.
Top level api
For the full api, see the API documentation.
This is an overview of most important functions available in the mobservable
namespace:
observable(value, options?)
Turns a value into a reactive array, object, function, value or a reactive reference to a value.
observer(reactJsComponent)
Provided by the mobservable-react
packaege, turns a ReactJS component into a reactive one, that automatically re-renders if any reactive data that it uses is changed.
extendObservable(target, properties)
Extends an existing object with reactive properties.
observe(function)
Similar to observable(function)
. Exception the created reactive function will not be lazy, so that it is executed even when it has no observers on its own.
Useful to bridge reactive code to imperative code.
What others are saying...
Elegant! I love it!
‐ Johan den Haan, CTO of Mendix
We ported the book Notes and Kanban examples to Mobservable. Check out the source to see how this worked out. Compared to the original I was definitely positively surprised. Mobservable seems like a good fit for these problems.
‐ Juho Vepsäläinen, author of "SurviveJS - Webpack and React" and jster.net curator
Great job with Mobservable! Really gives current conventions and libraries a run for their money.
‐ Daniel Dunderfelt
I was reluctant to abandon immutable data and the PureRenderMixin, but I no longer have any reservations. I can't think of any reason not to do things the simple, elegant way you have demonstrated.
‐David Schalk, fpcomplete.com
Contributing
- Feel free to send pr requests.
- Use
npm start
to run the basic test suite, npm test
for the test suite with coverage and npm run perf
for the performance tests.