Reputation: 3501
I am trying to take advantage of observables in angular2 and got confused on why should i use map()
over subscribe()
.
Suppose i am getting values from a webApi, like this
this.http.get('http://172.17.40.41:8089/api/Master/GetAllCountry')
Now using subscribe(success, error, complete)
I can get all the values on the success callback and I can return the values on the complete callback. If I can do all theses functionalities then what is the need of map()
? Does it give any advantage?
In short, why one should write like this:
this.http.get('http://172.17.40.41:8089/api/Master/GetAllCountry')
.map(r=>{})
.subscribe(value => {
}, error => error, () => {
});
when they can simply write this without the map function:
this.http.get('http://172.17.40.41:8089/api/Master/GetAllCountry')
.subscribe(value => {
}, error => error, () => {
});
Upvotes: 70
Views: 109438
Reputation: 31
When you need to manipulate an Observable array you would need to use something like RxJS map which will give you access to the array object as an array you can manipulate. In other words, you can't directly change/update an Observable array. You have to use RxJS to transform data like this:
filterTodos() {
// filter to show favorites only
this.todosList = this.todosList.pipe(
map((currentTodos: Todo[]) => {
return currentTodos.filter((currentTodo) =>
currentTodo.completed === true);
})
)
}
the RxJS map function transforms the todosList Observable array into one that can be manipulated. You have to use RxJS functions instead of array manipulation functions.
Use subscribe to listen to changes to an Observable. Use map, filter, etc to manipulate the Observable array. The RxJS map, filter is
Upvotes: 0
Reputation: 788
Observables are streams and they are designed to be written in functional streams. You should use RxJS operations because it is the 'functional' way of implementing subsctiptions to observables. Usually this happens when we take data outside of the Observable stream.
This is an asynchronous operation forced to work synchronously.
bad_example() {
let id;
this.obs.subscribe(param => id = param['id']);
this.get(id).subscribe(elem => this.elem = elem);
}
This is an asynchronous operation that works as supposed to work. (As a stream)
good_example() {
this.obs
.map(param => param['id'])
.switchMap(id => return this.get(id))
.subscribe(elem => this.elem = elem);
}
Upvotes: 3
Reputation: 21
.map()
is an rxjs operator, it will show the result in array []
form either .json()
form
https://www.learnrxjs.io/operators/transformation/map.html
Upvotes: 2
Reputation: 26312
Think map as a middleware which transforms the response.
this.http.get('http://172.17.40.41:8089/api/Master/GetAllCountry')
.map(r=>r.json())
.subscribe(result => {
// here result would have json object that was parsed by map handler...
},failurCallback,completeCallback)
subscribe is used to invoke the observable, please read a good doc on cold-vs-hot-observables
Upvotes: 35
Reputation: 5711
You need subscribe
to run your async request. If you just set map
- no requests will trigger. You can check.
Good practice to use map
to preproccess you data because many subscribers can comsume your results. So instead of adding preprocessing to each client (subscriber) you can prepare single output with single data schema for all.
Upvotes: 18
Reputation: 657248
If you want to return an Observable
some other code can subscribe to, but you still want to manipulate the data events in the current method, use map
.
The actual user of the observable needs to subscribe()
, because without subscribe()
the observable won't be executed at all. (forEach()
or toArray()
and probably others work as well to execute the observable instead of subscribe()
)
subscribe()
returns a Subscription
that can not be subscribed to, but it can be used to cancel the subscription.
map()
returns an Observable
which can be subscribed to.
Upvotes: 94