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
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
It seems that Rx.Subject has changed in a way that is no longer compatible with angular.equals(). Since you are using it in an object literal binding (input="{subject: $ctrl.someRxSubject}"), a new object will be created on each $digest and Angular will try to determine if it equals with the previous one (and break because of the new Rx.Subject implementation).
We have improved the way object/array literals are watched in #15301, but the change will land in 1.6.3. Here are your options:
Update to v1.6.3 (once it is released later this month) - heads-up: There are some breaking changes.
You can see it in action here.
Instead of binding to an object literal containing the Rx.Subject, create the object in your controller and bind to that (or bind to the Rx.Subject directly).
You can see these approaches in action here and there.
Closing, since we have already made the necessary improvements.
I have a very simple component, something like
Input is an object, so I am doing:
$ctrl.subject
was an RxJS 4, Subject, migrating to RxJS 5 this is causing aMaximum call stack size exceeded
error.If I do:
I dont have the issue. Any idea what can cause this?
The text was updated successfully, but these errors were encountered: