@Nagra’s solution is good but it will throw an error when executed from the client’s browser due to the Same-Origin Security Policies in effect. In essence, these security measures are there to prevent cross site requests that occur when the originator and the sender are on different domains. If you see errors like the below … Read more
Declarative event binding is only supported in static HTML in a components template. If you want to subscribe to events of elements dynamically added, you need to do it imperatively. elementRef.nativeElement.querySelector(…).addEventListener(…) or similar. If you want to be WebWorker-safe, you can inject the Renderer constructor(private elementRef:ElementRef, private renderer:Renderer) {} and use instead this.renderer.listen(this.elementRef.nativeElement, ‘click’, (event) … Read more
As mentioned in comments, you are looking for the flatMap operator. You can find more details in previous answers : How to do the chain sequence in rxjs Why do we need to use flatMap? Your example would read as : this.returnsObservable1(…) .flatMap(success => this.returnsObservable2(…)) .flatMap(success => this.returnsObservable3(…)) .subscribe(success => {(…)});
Well, let’s take the last question first. You can’t reliably unsubscribe from an event that you’ve subscribed to directly with a lambda expression. You either need to keep a variable around with the delegate in (so you can still use a lambda expression) or you need to use a method group conversion instead. Now as … Read more
subscribe isn’t deprecated, only the variant you’re using is deprecated. In the future, subscribe will only take one argument: either the next handler (a function) or an observer object. So in your case you should use: .subscribe({ next: this.handleUpdateResponse.bind(this), error: this.handleError.bind(this) }); See these GitHub issues: https://github.com/ReactiveX/rxjs/pull/4202 https://github.com/ReactiveX/rxjs/issues/4159