Length Event Fixes

standardize length event triggering

v1.0.23

Fixing list tests to work in all browsers

Maintain setter performance and fixes from 1.0.20

This change fixes #182 in a different way to avoid calling the getter code (which also might setup default functionality) when a property is set during initialization. This should maintain the performance of releases prior to 1.0.20.

Pull request: #186

Fix a bug with value definitions and initialization.

v1.0.18 fixed an issue where setting values on DefineMap initialization could cause unnecessary observations. The fix inadvertently introduced a bug where properties with value definitions were not ready to be set with new values at setup time. If you see errors like "Cannot set property prop of # which has only a getter" when creating DefineMaps in v1.0.18 or v1.0.19, upgrading to v1.0.20 will fix that.

More info:
#163
#182
#184

[Deprecated] use v1.0.20 or later

Upgrade can-util to 3.5.1

[Deprecated] use v1.0.20 or later

Fix DefineList length setter (#178)

Using can-util/js/log/log instead of console.log

#159

setter with default value bug fix

• #144 - fixed issue with setter and a default value causing an infinte loop
• #143 - fixed a link in the wildcard docs

.sort does not clone items

From #138, this fixes a bug where .sort() would create copies of every item in the list instead of just moving those items around.

`value` and async `set` work together

From #136, you can now use async setters like:

var Type = define.Constructor({
    prop: {
        value: 2,
        set: function(num, resolve){
            resolve( num * num );
        }
    }
});