Yesterday we released CanJS 2.2.6 with several bug fixes and memory improvements. As always, we recommend upgrading and if you run into issues feel free to get in touch with us on Gitter or create an issue on GitHub.
Here is the changelog:
- Fix calling define getters on map initialization
- Cleans up computes and fixes deep .attr calls.
- can/define with type: 'string' given values of null or undefined returns 'null' or 'undefined'
- Mangled file in AMD builds
- Compute memory leak with nested properties
- can.Model.findAll should reject if parseModels returns a non-array
data
property. - Cannot bind to future nested properties
- Check for vulnerability against iOS 8 object length bug
- can.stache helpers that rely on array replacement don't work, but work in can.mustache
- Helpers bind to nested properties differently in stache/mustache
- Cannot read value of property defined with "get" AND "set" methods
- Use Function.prototype.bind if available
- Compute code gets inserted into DOM with Stache sometimes
- Problem with defines called out of order
- can.compute nested key behaviour inconsistency with map bindings
- bug with component that has an if inside an inverse tag