We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When a finite stream is remembered and subscribed twice it behaves strangely.
import xs from 'xstream'; const userXs = xs.of(1, 2, 3) .remember() userXs.addListener({ next: (x) => bin.log("xs first: " + x), error: () => null, complete: () => bin.log("xs first: complete") }); // emits: ---1-2-3-| userXs.addListener({ next: (x) => bin.log("xs second: " + x), error: () => null, complete: () => bin.log("xs second: complete") }); // emits: ---3-1-2-3-| // expected: ---1-2-3-|
So the remembered value should reset after completion / when the first subscriber is disposed due to completion.
live example: http://www.webpackbin.com/4y9AjrnfZ
The text was updated successfully, but these errors were encountered:
fix(MemoryStream): fix tear down logic to reset memory
524d68e
On tear down, the MemoryStream should set *hasValue* to false. Fixes issue #36.
Version 2.6.1 released to fix this.
Sorry, something went wrong.
No branches or pull requests
When a finite stream is remembered and subscribed twice it behaves strangely.
So the remembered value should reset after completion / when the first subscriber is disposed due to completion.
live example: http://www.webpackbin.com/4y9AjrnfZ
The text was updated successfully, but these errors were encountered: