Releases: canjs/can-map-define
Releases · canjs/can-map-define
Add `resolver` behavior
This adds the value
behavior from DefineMap to can-map-define
. Since can-map-define
already has a behavior named value
(to set a starting value to a property), this new behavior has been named resolver
instead.
QUNIT2 upgrade
This updates the tests to use QUnit@2.x.x.
Incorrect documentation
Update to use Symbol instead of `__inSetup` property
Installed latest can-map
and using Symbol to replace __inSetup
property check.
Ref - canjs/canjs#4705
v4.3.4
getOwnEnumerableKeys accounts for default behavior values
This patch release fixes an issue with getOwnEnumerableKeys
ignoring the default behavior values:
var VM = CanMap.extend({
define: {
"*": {
serialize: false
},
notEnumerable: {
value: "no"
},
enumerableProp: {
serialize: true,
value: "yes"
},
notEnumerable2: {
serialize: false,
value: "maybe"
}
}
});
That meant, calling canReflect.getOwnEnumerableKeys
with instances of VM
will return all keys but notEnumerable2
. This release fixes that, so default behavior values are used first but any local property value can override the default.
Implement getOwnEnumerableKeys
v4.2.0
making hasKey work for functions
implementing can.hasKey Symbol
Updated docs, dependencies, and added cycle detection
- Update testee to the latest version 🚀 #38
- Update generator-donejs to the latest version 🚀 #39
- Remove generated API docs from the README #42
- Remove all prerelease package refs #44
- Add a cycle detection script to test process #48
- Update docs with new @parent & @collection #52
- Remove redundant docs #53