-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Atomic updates not working fully with streams inside other streams #179
Comments
Feel free to take a look at it to see if you spot any problems. |
Very cool, thank you for this! |
paldepind
added a commit
that referenced
this issue
Jul 11, 2018
The fix by @nordfjord is now on npm as version 0.2.8 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Creating a new issue out this bug that I found when working on #177
Basically when you have more complicated dependencies that are updated inside other streams, atomic updates break and you get more updates than you would expect.
Issue can be seen in a test case like this:
The assert fails with the value of 4 (and before the fix for #177 it would fail with the value of 3).
The text was updated successfully, but these errors were encountered: