Releases: canjs/can-define
Add support for value and oldValue in events
Fix warning code
Zero-argument getter warning updates
This release fixes two issues - It warns when you have type or Type with a zero argument getter and also fixes Default to warn even when the the default value is falsey (previously it only warned when default had non-falsey values)
(Updated) Tests using canReflect.getName in assertions fail in IE11
Test failed due to canReflect.getName
returning a certain value fail in IE11 because of how we name functions differently in IE11. With this fix, the tests use regular expressions to make the assertions less strict.
Updated More test with RegEx
Tests using canReflect.getName in assertions fail in IE11
Test failed due to canReflect.getName
returning a certain value fail in IE11 because of how we name functions differently in IE11. With this fix, the tests use regular expressions to make the assertions less strict.
Trying to set a getter that doesn't take `lastSet` throws an unhelpful error
When a getter had zero-arguments, it threw an unhelpful error: Error: can-reflect.setValue - Can not set value.
With this fix, an improved warning has been added to give users a better idea of what they've done wrong.
Warn on mutations done at unsafe times
Observable data should not be set while getters are running. With this update, users will be warned in development mode in cases where this is happening.
#454
[3.x Legacy] Fix @@can.offKeyValue / DefineList bug in v1.5.8
All handlers for a named property were being torn down if @@can.offKeyValue
was called on a DefineList. With this release, only the supplied handler is removed.
QUNIT2 upgrade
This updates the tests to use [email protected].
[3.x Legacy] Fix @@can.offKeyValue in DefineList for named properties
Listeners on named properties in DefineLists weren't unbinding correctly when using canReflect.offKeyValue()
to unbind. (removeEventListener/unbind/off were not affected by this issue). This release provides a fix to that issue.