All Versions
Latest Version
Avg Release Cycle
7 days
Latest Release
2496 days ago

Changelog History
Page 3

  • v0.18.2 Changes

    February 11, 2015

    🚀 This is not a bug fix release. The only purpose of this release is to allow the tutorial links on the README will be correct in external references to this project.


  • v0.18.1 Changes

    February 10, 2015
    • ⬆️ bump react-events 0.8.0 -> 0.8.1 - fdf4b09


  • v0.18.0 Changes

    February 09, 2015
    • ⚡️ update dependencies - e1eb0dd

    • react-mixin-manager 0.11.1 -> 0.11.2

    • react-events 0.7.9 -> 0.8.0

    Take a look at the new tutorials to help get the most out of react-backbone

    • ➕ add the responsive design tutorial - ac983da
    • ➕ add the forms tutorial - f5a4f4f
    • ➕ add collection handling / XHR totirial - dabc288

    • ➕ add the "validateField" 2 way binding option - aed43d9

    • 👉 make the "modelInvalidAware" mixin to reset state when the model changes - 6d8ee5b

    The bind input field can be the folling values

    • ⚡️ true to initiate 2-way binding (when the input field is updated, the model will be updated to match)
    • ⚡️ {validate: true} to validate the entire model when the field is updated
    • {validateField: true} to validate just the updated field


  • v0.17.2 Changes

    February 05, 2015
    • react-mixin-manager 0.10 -> 0.11 - 0bebe92

    ⚡️ All react-backbone mixins use the deferUpdate mixin from react-mixin-manager. deferUpdate has been updated to allow more explicit control of how long a forceRender is called after the component update request occurs. The default is 0 which should be good in most situations because most changes that would cause an update from model events would be within the same event loop. However, this provides additional global and component level options.

    ⚡️ See more details


  • v0.17.1 Changes

    January 29, 2015
    • 🛠 fix 2 way binding for composite RadioGroup component - 62f4c3c


  • v0.17.0 Changes

    January 28, 2015
    • ➕ add 2 way input field binding (using the bind={true} option) - 476ef03

    ⚡️ you can now use the bind attribute for any Backbone.input.* component to include 2-way binding support so the model will be updated as the input field is changed

      var Text = Backbone.input.Text;
      <Text name="foo" model={model} bind={true}/>
  • v0.16.0 Changes

    December 30, 2014
    • ➕ add multiple model/collection bindings to a single component - 4aa9be5

    Compatibility notes: 🚀 This is backwards compatible with the previous release but you can now have multiple managed models/collections for a single component. This can be useful if you want to monitor model changes or listen for XHR activity for more than 1 model/collection (or if you just don't like using the "model/collection" property and want a more custom property name for each component). See the docs for details but, an example is below

         // "modelChangeAware" will update the component when either the "foo" or "bar" models trigger a "change" event
          mixins: ['modelAware("foo", "bar")', 'modelChangeAware'],
          events: {
            'model:theEvent': function() {
              // will be executed when either the model assigned to the "foo" or the "bar" property triggers the "theEvent" event


  • v0.15.0 Changes

    December 12, 2014
    • null check on modelPopulate callback - 8362f80
    • requre jquery as last factory param - 6db6460
    • 📇 rename composite mixins to use a "backbone" prefix - 0f9fc42

    Compatibility notes: 👀 If you are using the input components (Backbone.input) you must add the jquery as an additional argument to the react-backbone method (see install instructions for details)

    require('react-backbone')(React, Backbone, _, $);

    The following mixin names have changed "XHRAware" is now "backboneXHRAware" "changeAware" is now "backboneChangeAware" "loadOn" is now "backboneLoadOn" ⚡️ "updateOn" is now "backboneUpdateOn"


  • v0.14.3 Changes

    December 11, 2014
    • 🚀 update dependencies (patch releases) - b2411a6
    • code cleanup - 83dad97


  • v0.14.2 Changes

    December 09, 2014
    • keep track of monitored xhr activity as state truthy value - 7bf735c You will now have a truthy value for state.loading instead of a boolean. This provides the ability to keep track of multiple simultaneous XHR requests (for example, a model fetch and collection fetch). Previously, state.loading would have gone to false after the first fetch returned (even if the second was still active)

    As long as you just comparing truthy values, no code changes are required. Do this:

        if (this.state.loading) {

    Do not do dhis

        if (this.state.loading === true) {