So the chain is really correct but the problem is that you’re creating an Observable and subscribe to it on every keyup event. That’s why it prints the same value multiple times. There’re simply multiple subscriptions which is not what you want to do. There’re obviously more ways to do it correctly, for example: @Component({ … Read more
Solution RxJS 5.4.2 should now work perfectly with TypeScript 2.4.1. Simply upgrade to 5.4.2+ if possible. npm install –save rxjs@^5.4.2 Then try restarting your editor and/or recompile if you don’t see an immediate change. If not, the below solution should work. Why it’s happening TypeScript 2.4 has a strictness change, and Subject<T> isn’t lifting to … Read more
This is a simple solution, as you said in your question. I think there’s nothing simpler than what you already provided. <input type=”text” [ngModel]=”subject | async” (ngModelChange)=”subject.next($event)” />
Be careful that you are using RxJS v5 while your documentation link seem to be RxJS v4. I don’t remember specifics but I think that the share operator went through some changes, in particular when it comes to completion and resubscription, but don’t take my word for it. Back to your question, as you have … Read more
I just came across a very similar issue while developing a custom module for a project. I’m not 100% sure we were having the same problem, but it looks pretty close. How I resolved my problem I would suggest deleting your node_modules folder and reinstalling all your dependencies. rm -rf node_modules/ npm cache clean npm … Read more
A Service in Angular is a singleton. This means that the service will exist for the entire lifespan of your application. The reason that you need to unsubscribe from an observable, is to avoid memory leaks. When do you get memory leaks? If something has been garbage collected while it was still subscribed to an … Read more
You can use concatAll() or mergeAll() without any parameter. dataFromBackend.pipe( tap(items => console.log(items)), mergeAll(), // or concatAll() ) This (including mergeMap) works only in RxJS 5+ because it treats Observables, arrays, array-like objects, Promises, etc. the same way. Eventually you could do also: mergeMap(val => from(val).pipe( tap(item => console.log(item)), map(item => item.name), )), toArray(), Jan … Read more
As @Adam and @Ploppy mentioned, the Observable.interval() is now deprecated not the preferred way of creating such an observable. The preferred way of doing this is via the IntervalObservable or TimerObservable. [currently in Typscript 2.5.2, rxjs 5.4.3, Angular 4.0.0] I wanted to add some usage to this answer to demonstrate what I found the best … Read more
As was pointed out by artur grzesiak in the comments, the BehaviorSubject interface was cleaned up, and the getter is now just myBehaviorSubject.value. I just wanted to add this as an answer because I almost didn’t read the comments to the original question, and would have missed the correct answer.
I would get the subscription and unsubscribe on it this way and not on the subject directly: ngOnInit() { this.pages$ = this.pagesService.getPagesListener(); this.subscription = this.pages$.subscribe((pages) => { // <——- this.pages = pages; console.log(pages); }); this.pagesService.getAll(); } ngOnDestroy() { this.subscription.unsubscribe(); // <——- }