observable

问题 I have 3 observables that i need to chain, result from first one is used in the other 2. They must run in order and each one must wait for the previous one to finish. Is it possible to chain then without nesting? public observable1(): Observable<Response> { let headers = new Headers(); headers.append("Content-Range", "bytes */*"); let requestOptions = new RequestOptions({headers: headers}); return this.http.put(url, "", requestOptions); } public observable2(data1url): Observable<Response> {

问题 I have 3 observables that i need to chain, result from first one is used in the other 2. They must run in order and each one must wait for the previous one to finish. Is it possible to chain then without nesting? public observable1(): Observable<Response> { let headers = new Headers(); headers.append("Content-Range", "bytes */*"); let requestOptions = new RequestOptions({headers: headers}); return this.http.put(url, "", requestOptions); } public observable2(data1url): Observable<Response> {

问题 i have a angular component, that uses 3 services. Each of those services has an observer, that i can subscribe to. The view of the component must be updated, if anything on the observed changes, that happens through websockets (feathers.js). I want the doSomethingWithTheNewDataThatIsShownOnView() to be called only once on ngInit and i think, i can do this with forkJoin: private ngOnInit(): void { Observable.forkJoin( this.filesService.inputs$, this.filesService.outputs$, this.processesService

问题 Struggling a bit too long here. I have two tables in Firebase: accounts LJHGGKJH prop1: 'val' prop2: 'val' IUYIUTJF prop1: 'val' prop2: 'val' locations_per_account LJHGGKJH 0: [1, 5, 6] IUYIUTJF 0: [5, 2, 8] As you see accounts item's unique key points to locations_per_account item's unique key - if they match they belongs to the same user. Now I want to make one method in my service which would provide me observable of every account and its locations, so I could use async pipe in my template

问题 I'm banging my head against the wall with observables. Almost all of the documentation I can find is in the older rxjs syntax. I have an API call which is an observable. I'm calling it elsewhere and subscribing to it - trying to populate a table with the data from this GET request. If I simply console.log my getData function, it logs the subscription rather than my data. I can successfully console.log data within the .subscribe function, but I want to use data outside of .subscribe() . How do

问题 I'm banging my head against the wall with observables. Almost all of the documentation I can find is in the older rxjs syntax. I have an API call which is an observable. I'm calling it elsewhere and subscribing to it - trying to populate a table with the data from this GET request. If I simply console.log my getData function, it logs the subscription rather than my data. I can successfully console.log data within the .subscribe function, but I want to use data outside of .subscribe() . How do

问题 I'm banging my head against the wall with observables. Almost all of the documentation I can find is in the older rxjs syntax. I have an API call which is an observable. I'm calling it elsewhere and subscribing to it - trying to populate a table with the data from this GET request. If I simply console.log my getData function, it logs the subscription rather than my data. I can successfully console.log data within the .subscribe function, but I want to use data outside of .subscribe() . How do

问题 I use Observables in couchbase. What is the difference between Schedulers.io() and Schedulers.computation() ? 回答1: From the documentation of rx: Schedulers.computation( ) - meant for computational work such as event-loops and callback processing; do not use this scheduler for I/O (use Schedulers.io( ) instead); the number of threads, by default, is equal to the number of processors Schedulers.io( ) - meant for I/O-bound work such as asynchronous performance of blocking I/O, this scheduler is

问题 I use Observables in couchbase. What is the difference between Schedulers.io() and Schedulers.computation() ? 回答1: From the documentation of rx: Schedulers.computation( ) - meant for computational work such as event-loops and callback processing; do not use this scheduler for I/O (use Schedulers.io( ) instead); the number of threads, by default, is equal to the number of processors Schedulers.io( ) - meant for I/O-bound work such as asynchronous performance of blocking I/O, this scheduler is

问题 I'm doing unit testing with Jasmine/Karma against an Angular service. I'd like to confirm that my service properly filters items. For example, if I have a service to get people over a certain age, it should return people over the minimum age (positive case) should NOT return people under a the minimum age (negative case) It's #2 that I'm struggling to test. The service: getPeople(minAge: number): Observable<string> { const source = Observable.from([ { name: 'Joe', age: 30 }, { name: 'Frank',