Releases: canjs/can-component
Releases · canjs/can-component
Removes use of nodeLists
Include `new Component()` mutations with logStack
Now mutations are visible in queues.logStack
when a component instantiated programmatically like the following:
var c = new Component({
viewModel : {
foo: value.bind(this,"bar")
}
});
QUNIT2 upgrade
This updates the tests to use QUnit@2.x.x.
Fix test using code not compatible with IE11
v4.6.1 4.6.1
initializeBindings: false and memory leak fixes
This release fixes memory leaks and provides a new option to use with SSR. When initializing a component that might never be added to the page, using {initializeBindings: false}
will prevent bindings from being setup until it is.
let component = new MyComponent({
initializeBindings: false
});
// Doesn't leak if not inserted!
Replaces can-dom-data-state with can-dom-data
v4.5.4 4.5.4
Ensure memory is cleaned up when components are never inserted
Add deprecation notices in the docs
This adds deprecation notices about the following features:
Fix viewModel function that returns a new type
This fixes the viewModel
function that returns a new type like the following:
Component.extend({
tag: "foo-bar",
viewModel: function(attrs) {
return CanMap.extend({
foo: "bar"
});
}
});
Fix highlighting in the docs
Fix highlight typo #331