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
Observable.from can take string and iterate it as
Observable.from
Rx.Observable.from('foo').subscribe(console.log); // => Next: f // => Next: o // => Next: o // => Completed
but fails to do it on some browsers does not support string iterator (IE, for example)
in RxJS4, seems it has own iterator for string object (https://github.com/Reactive-Extensions/RxJS/blob/master/src/core/linq/observable/from.js#L3-L23) to support this behavior - does RxJS5 need to port same behavior?
I've used https://jsfiddle.net/v0w220v6/ to test out between different browsers.
The text was updated successfully, but these errors were encountered:
related to #998 .
Sorry, something went wrong.
I believe some of the infrastructure for this is already in place. So there might be a bug.
I assume it's StringIteratror in IteratorObservable, will try to look into what's happening. Marking this as bug meanwhile.
StringIteratror
IteratorObservable
fix(fromObservable): expand compatibility for iterating string source
f30dca9
closes ReactiveX#1147
8f7924f
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
kwonoj
Successfully merging a pull request may close this issue.
Observable.from
can take string and iterate it asbut fails to do it on some browsers does not support string iterator (IE, for example)
in RxJS4, seems it has own iterator for string object (https://github.com/Reactive-Extensions/RxJS/blob/master/src/core/linq/observable/from.js#L3-L23) to support this behavior - does RxJS5 need to port same behavior?
I've used https://jsfiddle.net/v0w220v6/ to test out between different browsers.
The text was updated successfully, but these errors were encountered: