test recursive deferred update of computed #3

Closed
mbest opened this Issue Mar 25, 2012 · 1 comment

Comments

Projects
None yet
1 participant
@mbest
Owner

mbest commented Mar 25, 2012

Test what happens if a computed observable causes an update to itself recursively.

@mbest

This comment has been minimized.

Show comment Hide comment
@mbest

mbest Apr 3, 2012

Owner

Decided to test a different recursive scenario where two computed are dependent on each other. An update to one causes an update to other, and back and forth, forever. Strangely, Chrome didn't report an error although execution did not continue past the update. The infinite recursion was caused by the dirty notifications.

Owner

mbest commented Apr 3, 2012

Decided to test a different recursive scenario where two computed are dependent on each other. An update to one causes an update to other, and back and forth, forever. Strangely, Chrome didn't report an error although execution did not continue past the update. The infinite recursion was caused by the dirty notifications.

mbest added a commit that referenced this issue Apr 4, 2012

computed observable only does "dirty" notification when update is don…
…e/scheduled. This prevents recursive notifications when computed observables depend on each other. See #3.

@mbest mbest closed this Apr 4, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment