Comment on page
Angular Questions And Answers
Observables are declarative—that is, you define a function for publishing values, but it is not executed until a consumer subscribes to it. The subscribed consumer then receives notifications until the function completes, or until they unsubscribe.
It is what we want to observe, which will be implemented through a collection of future events or values. An observable can be created from user events derived from the use of a form, an HTTP call, a data store, etc.
A representation of any set of values over any amount of time. This is the most basic building block of RxJS.
Answer: Angular components enter its lifecycle from the time it is created to the time it is destroyed. Angular hooks provide ways to tap into these phases and trigger changes at specific phases in a lifecycle.
ngOnChanges( ): This method is called whenever one or more input properties of the component changes. The hook receives a SimpleChanges object containing the previous and current values of the property.
ngOnInit( ): This hook gets called once, after the ngOnChanges hook.
It initializes the component and sets the input properties of the component.
ngDoCheck( ): It gets called after ngOnChanges and ngOnInit and is used to detect and act on changes that cannot be detected by Angular.
We can implement our change detection algorithm in this hook.
ngAfterContentInit( ): It gets called after the first ngDoCheck hook. This hook responds after the content gets projected inside the component.
ngAfterContentChecked( ): It gets called after ngAfterContentInit and every subsequent ngDoCheck. It responds after the projected content is checked.
ngAfterViewInit( ): It responds after a component's view, or a child component's view is initialized.
ngAfterViewChecked( ): It gets called after ngAfterViewInit, and it responds after the component's view, or the child component's view is checked.
ngOnDestroy( ): It gets called just before Angular destroys the component. This hook can be used to clean up the code and detach event handlers.
Answer: Yes, we can, with Angular Universal, a technology provided by Angular capable of rendering applications on the server-side.
Dependency injection in Angular are services that have functionality. Various components and directives in an application can need these functionalities of the service. Angular provides a smooth mechanism by which these dependencies are injected into components and directives.
Following code demonstrates how to navigate between different routes in an Angular app dubbed “Some Search App”:
import from "@angular/router";
.
.
.
@Component({
selector: 'app-header',
template: `
<nav class="navbar navbar-light bg-faded">
<a class="navbar-brand" (click)="goHome()">Some Search App</a>
<ul class="nav navbar-nav">
<li class="nav-item">
<a class="nav-link" (click)="goHome()">Home</a>
</li>
<li class="nav-item">
<a class="nav-link" (click)="goSearch()">Search</a>
</li>
</ul>
</nav>
`
})
class HeaderComponent {
constructor(private router: Router) {}
goHome() {
this.router.navigate(['']);
}
goSearch() {
this.router.navigate(['search']);
}
}
An angular application consists of components and templates which a browser cannot understand. Therefore, every Angular application needs to be compiled before running inside the browser. The Angular compiler takes in the JS code, compiles it, and then produces some JS code. It is known as AOT compilation and happens only once per occasion per user.
There are two kinds of compilation that Angular provides:
- 1.JIT(Just-in-Time) compilation: the application compiles inside the browser during runtime
- 2.AOT(Ahead-of-Time) compilation: the application compiles during the build time.
- Fast Rendering: The browser loads the executable code and renders it immediately as the application is compiled before running inside the browser.
- Fewer Ajax Requests: The compiler sends the external HTML and CSS files along with the application, eliminating AJAX requests for those source files.
- Minimizing Errors: Easy to detect and handle errors during the building phase.
- Better Security: Before an application runs inside the browser, the AOT compiler adds HTML and templates into the JS files, so there are no extra HTML files to be read, thus providing better security for the application.
- 1.How to trigger change detection manually?
- 2.What is the difference between
detectChangesandmarkForCheck? Scenario: @Input changed and component has not been refreshed.
Angular's default change detection strategy may work well for a hobby app or presentation demo but if you're dealing with a large or enterprise application, you're likely going to take a performance hit. That's because by default Angular checks and detects everything rendered in the template. One of the ways we can solve this is by using manual change detection, however, it's not the best way.
True "manual" change detection in Angular would be a combination of the OnPush change detection strategy with methods like
detectChanges(), detach(), markForCheck() and others in your components. This can be a great solution if you need full control over change detection. For instance, if you're getting data from a websocket you may want to use detectChanges() to limit how often you're checking for changes. If you don't need full control, however, it can certainly over-complicate things.ngOnChanges( ): This method is called whenever one or more input properties of the component changes. The hook receives a SimpleChanges object containing the previous and current values of the property.
ngOnInit( ): This hook gets called once, after the ngOnChanges hook. It initializes the component and sets the input properties of the component.
ngDoCheck( ): It gets called after ngOnChanges and ngOnInit and is used to detect and act on changes that cannot be detected by Angular. We can implement our change detection algorithm in this hook.
ngAfterContentInit( ): It gets called after the first ngDoCheck hook. This hook responds after the content gets projected inside the component.
ngAfterContentChecked( ): It gets called after ngAfterContentInit and every subsequent ngDoCheck. It responds after the projected content is checked.
ngAfterViewInit( ): It responds after a component's view, or a child component's view is initialized.
ngAfterViewChecked( ): It gets called after ngAfterViewInit, and it responds after the component's view, or the child component's view is checked.
ngOnDestroy( ): It gets called just before Angular destroys the component. This hook can be used to clean up the code and detach event handlers.
There's an Observable field in a component, it got subscribed to. Can you spot a memory leak? (it should be unsubscribed from inngOnDestroy)
In Angular, annotations are used for creating an annotation array. They are only metadata set of the class using the Reflect Metadata library.
Decorators in Angular are design patterns used for separating decoration or modification of some class without changing the original source code.
A Promise is always asynchronous, while an Observable can be either synchronous or asynchronous, a Promise can provide a single value, whereas an Observable is a stream of values (from 0 to multiple values), you can apply RxJS operators to an Observable to get a new tailored stream.
One of the key features of Observables is its ability to cancel the underlying operation of the source. In fact, the ReactiveX documentation explains the primary purpose of the
Subscription as this.Subscription: represents the execution of an Observable, is primarily useful for cancelling the execution.
However, if you have been using RxJS for long enough, this is not a concept that seems natural to
Observables. The pattern seems to almost dictate that Subscriptions are simply a “viewership” to the source and not something that controls the source. This is mostly because of the different types of Observables that we come to use and our inability to always know what type an observable is and what really happens when you do unsubscribe from the Subscription.When you
subscribe you are essentially just starting to listen. Similarly when you unsubscribe you are stopping your listening. Following is a classic example of a hot observable.The observable is already working and streaming data. A realworld example might be when you enter in a life-stream movie, the movie is already streaming no matters if you are subscribed or not. Example,behaviorSubject
On cold observables, the observer starts the underlying operation for that observer with a
subscribe. Similarly, the observer ends the underlying operation for that observer with an unsubscribe. Most creation operators create a cold observable.The observable does not stream data to the subscriptor until such is subscribed. A realworld example might be if you visit Netflix and start a movie, the movie will be displayed when you "subscribe" to it.
BehaviorSubject is a type of subject, a subject is a special type of observable so you can subscribe to messages like any other observable. The unique features of BehaviorSubject are:
- It needs an initial value as it must always return a value on subscription even if it hasn't received a
next() - Upon subscription, it returns the last value of the subject. A regular observable only triggers when it receives an
onnext - at any point, you can retrieve the last value of the subject in a non-observable code using the
getValue()method.
In addition, you can get an observable from behavior subject using theasObservable()method onBehaviorSubject.
// Behavior Subject
// a is an initial value. if there is a subscription
// after this, it would get "a" value immediately
let bSubject = new BehaviorSubject("a");
bSubject.next("b");
bSubject.subscribe(value => {
console.log("Subscription got", value); // Subscription got b,
// ^ This would not happen
// for a generic observable
// or generic subject by default
});
bSubject.next("c"); // Subscription got c
bSubject.next("d"); // Subscription got d
// Regular Subject
let subject = new Subject();
subject.next("b");
subject.subscribe(value => {
console.log("Subscription got", value); // Subscription wont get
// anything at this point
});
subject.next("c"); // Subscription got c
subject.next("d"); // Subscription got d