-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
Requires complete listener #1
Comments
Hi, thank you for taking your time to send us this issue. We appreciate it, however, this is by design. It's required, for two reasons:
If you don't need to listen to error nor complete, just pass a noop function I'll close this issue unless after discussion we agree that it would make sense to change. Thank you for your time and I hope it's ok with you. |
That's totally fine with me, thank you for the response and great work! |
So just using this very basic example below to start messing around with xstream in Node.JS it looks like the code assumes there is a "complete" event handler. If I remove it it actually throws an exception when it triggers because it's trying to a run a function that does not exist.
Using Node.js 5.10.1 and Xstream 1.0.2
The text was updated successfully, but these errors were encountered: