Showing posts with label Subscribe. Show all posts
Showing posts with label Subscribe. Show all posts
Sunday, August 23, 2020
Consuming Observables using async pipe
To consume an Observable using async pipe we need to use the |
async syntax in the components view template. In the previous post, we saw how to consume an Observable (response from a http API call) by subscribing
to the Observable.
The view template consumes this Observable and displays the response from the http call in the View template. The async pipe automatically subscribes and unsubscribes to the Observable, whenever a new value is emitted from the Observer the async pipe automatically detects the change and refreshes the component.
The view template consumes this Observable and displays the response from the http call in the View template. The async pipe automatically subscribes and unsubscribes to the Observable, whenever a new value is emitted from the Observer the async pipe automatically detects the change and refreshes the component.
Consuming Observable using Subscribe
To consume an observable by subscribing, we need to call the
subscribe() method and capture the result/error objects returned by the
observable. In this sample, we will get a list of users using a http.get call
which returns an observable.
Creating Observable
We can create our own Observable by creating a function that takes an observer parameter.
The function will be passed to create the Observable. When someone subscribes
to the observable, the function is called and returns the values emitted from
the function.
In the below sample we create a function listGenerator, which takes an observer as a parameter and emit list values one at a time using .next().
In the below sample we create a function listGenerator, which takes an observer as a parameter and emit list values one at a time using .next().
Friday, August 21, 2020
What is an Observable?
The observer pattern
is a software design pattern in which an object, called the subject, maintains
a list of its dependents, called observers, and notifies them automatically of
state changes. Observables get their name from the
Observer design pattern. The Observable
sends notifications while the Observer
receives them.
Subscribe to:
Posts (Atom)

