Changelog History
Page 2
-
v0.23.3 Changes
March 23, 2015- react-mixin-manager 0.13.0 -> 0.13.1 - 8d00da2
-
v0.23.2 Changes
March 20, 2015โก๏ธ Optimize model/collection cache usage
-
v0.23.1 Changes
March 20, 2015- optimizations - 5cb4f6a
- โ remove setModel/setCollection - 6308926
Compatibility notes: ๐ This should really be a minor release but I just did one yesterday and it hasn't touched too many people - and no one should really be using setModel/setCollection methods.
Using setModel will override any property change (because it sets to state). Because of this, I want to be more explicit about what is happening. You can still do this but you must use getInitialState instead
getInitialState: function() { return { model: myModel } }
-
v0.23.0 Changes
March 19, 2015- ensure models/collections from state have correct event bindings - 06c6b28
- โก๏ธ prevent loading state updates on collections from sub-model XHR activity - 158e48c
- (optimization) prevent setState call with 2nd concurrent XHR event - beaec7f
- backbone-xhr-events 0.11.2 -> 0.12.0 - 430e78e
-
v0.22.1 Changes
March 17, 2015- ๐ bug fix: allow XHRAware mixin to be aware of current XHR activity during a model/collection property change - 77c8d27
-
v0.22.0 Changes
February 28, 2015- โ add modelFetch / collectionFetch mixin - 49a2f58
- โ remove ability to use "new" as modelAware parameter - e267711
๐ The
new
modelAware/collectionAware
special mixin parameter has been removed because, after second thought, this promotes using state for models which is an anti-pattern.A
modelFetch
andcollectionFetch
mixin has been added which will ensure that any bound models or collections will be fetched when the component is mounted (but they will not be fetch if they are already populated or currently fetching). -
v0.21.1 Changes
February 22, 2015- ๐ allow modelAware/collectionAware to create new models/collections - 18801d6
The following details are for the
modelAware
mixin but can also be applied tocollectionAware
.The
new
keyword can be used as the modelAware parameter if a new model should be created. The model class must be provided as theModel
component attribute. The react component properties will be provided as the model constructor argument.React.createClass({ mixins: ['modelAware("new")'], Model: MyModelClass, render: function() { // model will be a new instance of MyModelClass var model = this.getModel(); } } });
new:fetch
can be used instead ofnew
to auto-fetch the model as well. For example, the following code examples are functionally the same.Without the
new:fetch
modelAware paramReact.createClass({ mixins: ['modelAware'], getInitialState: function() { var model = new MyModel(this.props); model.fetch(); this.setModel(model); return null; } });
With the
new:fetch
modelAware paramReact.createClass({ mixins: ['modelAware("new:fetch")'], Model: MyModelClass });
-
v0.21.0 Changes
February 20, 2015- backbone-xhr-events -0.9.5 -> 0.11.2 - cecd748
๐ See backbone-xhr-events release notes for more details but there are API changed if you are using the advanced XHR lifecycle binding (if you bind to any "xhr" events). If you do not, no changes need to be made in your app
-
v0.20.0 Changes
February 15, 2015- react-mixin-manager 0.12.0 -> 0.13.0 & react-events 0.8.1 -> 0.9.0 - e99863d
- โ add react-mixin-manager 0.12.0 hard dependency notification - 5e9eddc
๐ incorporate the latest namespece-related changes for react-mixin-manager and react-events. There was a notable API change in react-mixin-manager which you can see with the react-mixin-manager/release-notes.md. (basically the React.mixins.replace method was removed and React.mixins.add will always replace).
๐ Getting close to a 1.0 release
-
v0.19.0 Changes
February 14, 2015- ๐ use "react-backbone" namespace - 9789aa1
You must upgrade to react-mixin-manager 0.12.0
๐ Any mixin can be prefixed with "react-backbone". This allows if reuse the react-backbone mixin names if desired.
For example
mixins: ['react-backbone.modelAware']