The React v0.12 release announcement included the following:

New Features:

* React.addons.batchedUpdates added to API for hooking into update cycle

However I cannot find any documentation for this API. What is its purpose?

Specifically, any chance that it has an equivalent of Ember.run()?

The React v0.12 release announcement included the following:

New Features:

* React.addons.batchedUpdates added to API for hooking into update cycle

However I cannot find any documentation for this API. What is its purpose?

Specifically, any chance that it has an equivalent of Ember.run()?

• javascript
• reactjs

2 Answers 2

When responding to synthetic events like onClick and so on, ponent state changes are batched so lots of calls to this.setState for the same ponent will only result in one render.

If you are changing state in response to some other async callback (e.g. AJAX or setTimeout) then every call to this.setState will result in a render. You can wrap your work in batchedUpdates(..) to avoid this.

var React = require('react/addons');
var batchedUpdates = React.addons.batchedUpdates;
var request = require('superagent'); // AJAX lib

var req = request('GET', ...).end(function(err, res) {
    // invoked when AJAX call is done
    batchedUpdates(function(){
        .. all setState calls are batched and only one render is done ...
    })
});

The default batched update strategy is great for your average website. Sometimes you have extra requirements and need to deviate from that.

The initial reason this was made public is for a requestAnimationFrame batching strategy, which is better for games and sites that need to update often and in many places.

It's just an extensibility point to solve edge case issues.