You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously (at least in CanJS 3.2), the behavior for can Map getters would behave one way in respect to setting a value. In 3.11, the behavior has changed.
In 3.2, if a getter had a listener registered on it, the response would be the result of any setter that was previously run. If there was NO listener, than the result would be the result of the getter compute.
In 3.11, regardless if there is a listener or not, the result is always the getter function result.
Previously (at least in CanJS 3.2), the behavior for can Map getters would behave one way in respect to setting a value. In 3.11, the behavior has changed.
In 3.2, if a getter had a listener registered on it, the response would be the result of any setter that was previously run. If there was NO listener, than the result would be the result of the getter compute.
In 3.11, regardless if there is a listener or not, the result is always the getter function result.
3.2 JSBin: http://jsbin.com/fakive/11/edit?js,console
3.11 JSBin: http://jsbin.com/ruponoc/11/edit?js,console
Basically, there needs to be some way to get the old behavior as this caused breaking changes.
The text was updated successfully, but these errors were encountered: