Rx offers both behaviors (as well as others). The different Rx Subjects available can let you explore the different ways observables can behave: the Rx.Subject is the most basic fire-and-forget variety — if you were not subscribed when the event happened, then you do not see it. Use new Rx.BehaviorSubject(undefined) instead of Subject and you … Read more
The reason why they’re using of() is because it’s very easy to use it instead of a real HTTP call. In a real application you would implement getHeroes() like this for example: getHeroes(): Observable<Hero[]> { return this.http.get(`/heroes`); } But since you just want to use a mocked response without creating any real backend you can … Read more
Don’t overthink it. @ViewChild(‘button’) button; clicks$:Observable<any>; ngOnInit() { this.clicks$ = Observable.fromEvent(this.button.nativeElement, ‘click’); }
Please include your view and model next time (app/about/about.html and about.model). If you are returning an array, you can use the asyncPipe, which “subscribes to an Observable or Promise and returns the latest value it has emitted. When a new value is emitted, the async pipe marks the component to be checked for changes” hence … Read more
You will need to subscribe to your observables: this.CountryService.GetCountries() .subscribe(countries => { this.myGridOptions.rowData = countries as CountryData[] }) And, in your html, wherever needed, you can pass the async pipe to it.
This is really different, React is view library and Rxjs is reactive programming library for javascript. You can use Rxjs inside react view but in reactjs, people usually use a library like Redux, flux, mobx or relayjs (if they use graphql) for data flow.
The equivalent of then for observables would be flatMap. You can see some examples of use here : RxJS Promise Composition (passing data) Why we need to use flatMap? RxJS sequence equvalent to promise.then()? For your example, you could do something like : this._myService.doSomething() .flatMap(function(x){return functionReturningObservableOrPromise(x)}) .flatMap(…ad infinitum) .subscribe(…final processing) Pay attention to the types … Read more
Instead of this: catchError((error) => { this.authService.signOut(); return throwError(error); }), You could try this: catchError((error) => { this.authService.signOut(); return throwError(() => error); }), I wasn’t able to test it thoroughly, but a simple attempt seemed to work. This was my simple test (using RxJS v7.2): Service getProducts(): Observable<IProduct[]> { return this.http.get<IProduct[]>(this.productUrl) .pipe( tap(data => console.log(‘All: … Read more
Only the overloads that accept a scheduler are deprecated. The variant that you are using is not deprecated, see https://github.com/ReactiveX/rxjs/blob/master/src/internal/observable/of.ts
Short answer: It’s not possible. How to work with this: The basic concept of RxJS is that any error or complete-call will basically “kill” a stream. This concept forces you not “just to throw around errors here and there as you please” but to handle errors and the flow of data within your application properly. … Read more