Downward Triangle Star Pattern in JavaScript to create a downward triangle star pattern use a nested loops, it's also known as a reverse star patterns. From the above-shown patterns, you can see the numbers of stars decreases from 'n' to 1.
Angular is a TypeScript-based open-source front-end platform that makes it easy to build web, mobile and desktop applications. The major features of this framework include declarative templates, dependency injection, end to end tooling which ease application development.
TypeScript is a strongly typed superset of JavaScript created by Microsoft that adds optional types, classes, async/await and many other features, and compiles to plain JavaScript. Angular is written entirely in TypeScript as a primary language. You can install TypeScript globally as
Component: These are the basic building blocks of an Angular application to control HTML views.
Modules: An Angular module is a set of angular basic building blocks like components, directives, services etc. An application is divided into logical pieces and each piece of code is called as "module" which perform a single task.
Templates: These represent the views of an Angular application.
Services: Are used to create components which can be shared across the entire application.
Metadata: This can be used to add more data to an Angular class.
Components are the most basic UI building block of an Angular app, which form a tree of Angular components. These components are a subset of directives. Unlike directives, components always have a template, and only one component can be instantiated per element in a template. Let's see a simple example of Angular component
import{Component}from'@angular/core';
@Component({selector: 'my-app',template: ` <div> <h1>{{title}}</h1> <div>Learn Angular6 with examples</div> </div> `,})exportclassAppComponent{title: string='Welcome to Angular world';}
A template is a HTML view where you can display data by binding controls to properties of an Angular component. You can store your component's template in one of two places. You can define it inline using the template property, or you can define the template in a separate HTML file and link to it in the component metadata using the @Component decorator's templateUrl property.
Modules are logical boundaries in your application and the application is divided into separate modules to separate the functionality of your application. Lets take an example of app.module.ts root module declared with @NgModule decorator as below,
Angular application goes through an entire set of processes or has a lifecycle right from its initiation to the end of the application. The representation of lifecycle in pictorial representation as follows,
The description of each lifecycle method is as below,
ngOnChanges: When the value of a data bound property changes, then this method is called.
ngOnInit: This is called whenever the initialization of the directive/component after Angular first displays the data-bound properties happens.
ngDoCheck: This is for the detection and to act on changes that Angular can't or won't detect on its own.
ngAfterContentInit: This is called in response after Angular projects external content into the component's view.
ngAfterContentChecked: This is called in response after Angular checks the content projected into the component.
ngAfterViewInit: This is called in response after Angular initializes the component's views and child views.
ngAfterViewChecked: This is called in response after Angular checks the component's views and child views.
ngOnDestroy: This is the cleanup phase just before Angular destroys the directive/component.
Data binding is a core concept in Angular and allows to define communication between a component and the DOM, making it very easy to define interactive applications without worrying about pushing and pulling data. There are four forms of data binding(divided as 3 categories) which differ in the way the data is flowing.
From the Component to the DOM:
Interpolation: {{ value }}: Adds the value of a property from the component
Property binding: [property]=”value”: The value is passed from the component to the specified property or simple HTML attribute
<inputtype="email" [value]="user.email">
From the DOM to the Component:Event binding: (event)=”function”: When a specific DOM event happens (eg.: click, change, keyup), call the specified method in the component
<button(click)="logout()"></button>
Two-way binding:Two-way data binding: [(ngModel)]=”value”: Two-way data binding allows to have the data flow both ways. For example, in the below code snippet, both the email DOM input and component email property are in sync
Metadata is used to decorate a class so that it can configure the expected behavior of the class. The metadata is represented by decorators
Class decorators, e.g. @Component and @NgModule
import{NgModule,Component}from'@angular/core';
@Component({selector: 'my-component',template: '<div>Class decorator</div>',})exportclassMyComponent{constructor(){console.log('Hey I am a component!');}}
@NgModule({imports: [],declarations: [],})exportclassMyModule{constructor(){console.log('Hey I am a module!');}}
Property decorators Used for properties inside classes, e.g. @Input and @Output
Angular CLI(Command Line Interface) is a command line interface to scaffold and build angular apps using nodejs style (commonJs) modules. You need to install using below npm command,
npm install @angular/cli@latest
Below are the list of few commands, which will come handy while creating angular projects
Creating New Project: ng new
Generating Components, Directives & Services: ng generate/g The different types of commands would be,
ng generate class my-new-class: add a class to your application
ng generate component my-new-component: add a component to your application
ng generate directive my-new-directive: add a directive to your application
ng generate enum my-new-enum: add an enum to your application
ng generate module my-new-module: add a module to your application
ng generate pipe my-new-pipe: add a pipe to your application
ng generate service my-new-service: add a service to your application
What is the difference between constructor and ngOnInit?
The Constructor is a default method of the class that is executed when the class is instantiated and ensures proper initialisation of fields in the class and its subclasses. Angular, or better Dependency Injector (DI), analyses the constructor parameters and when it creates a new instance by calling new MyClass() it tries to find providers that match the types of the constructor parameters, resolves them and passes them to the constructor. ngOnInit is a life cycle hook called by Angular to indicate that Angular is done creating the component. Mostly we use ngOnInit for all the initialization/declaration and avoid stuff to work in the constructor. The constructor should only be used to initialize class members but shouldn't do actual "work". So you should use constructor() to setup Dependency Injection and not much else. ngOnInit() is better place to "start" - it's where/when components' bindings are resolved.
exportclassAppimplementsOnInit{constructor(privatemyService: MyService){//called first time before the ngOnInit()}ngOnInit(){//called after the constructor and called after the first ngOnChanges()//e.g. http call...}}
A service is used when a common functionality needs to be provided to various modules. Services allow for greater separation of concerns for your application and better modularity by allowing you to extract common functionality out of components.
Let's create a repoService which can be used across components,
import{Injectable}from'@angular/core';import{Http}from'@angular/http';
@Injectable({// The Injectable decorator is required for dependency injection to work// providedIn option registers the service with a specific NgModuleprovidedIn: 'root',// This declares the service with the root app (AppModule)})exportclassRepoService{constructor(privatehttp: Http){}fetchAll(){returnthis.http.get('https://api.github.com/repositories');}}
The above service uses Http service as a dependency.
Dependency injection (DI), is an important application design pattern in which a class asks for dependencies from external sources rather than creating them itself. Angular comes with its own dependency injection framework for resolving dependencies( services or objects that a class needs to perform its function).So you can have your services depend on other services throughout your application.
Injectors in Angular have rules that can be leveraged to achieve the desired visibility of injectables in your applications. By understanding these rules, you can determine in which NgModule, Component, or Directive you should declare a provider.
Angular has two injector hierarchies:
Module injector
When angular starts, it creates a root injector where the services will be registered, these are provided via injectable annotation. All services provided in the ng-model property are called providers (if those modules are not lazy-loaded).
Angular recursively goes through all models which are being used in the application and creates instances for provided services in the root injector. If you provide some service in an eagerly-loaded model, the service will be added to the root injector, which makes it available across the whole application.
Platform Module
During application bootstrapping angular creates a few more injectors, above the root injector goes the platform injector, this one is created by the platform browser dynamic function inside the main.ts file, and it provides some platform-specific features like DomSanitizer.
NullInjector()
At the very top, the next parent injector in the hierarchy is the NullInjector().The responsibility of this injector is to throw the error if something tries to find dependencies there, unless you've used @Optional() because ultimately, everything ends at the NullInjector() and it returns an error or, in the case of @Optional(), null.
ElementInjector
Angular creates ElementInjector hierarchies implicitly for each DOM element. ElementInjector injector is being created for any tag that matches the angular component, or any tag on which directive is applied, and you can configure it in component and directive annotations inside the provider's property, thus, it creates its own hierarchy likewise the upper one.
The AsyncPipe subscribes to an observable or promise and returns the latest value it has emitted. When a new value is emitted, the pipe marks the component to be checked for changes.
Let's take a time observable which continuously updates the view for every 2 seconds with the current time.
@Component({selector: 'async-observable-pipe',template: `<div><code>observable|async</code>: Time: {{ time | async }}</div>`})exportclassAsyncObservablePipeComponent{time: Observable<string>;constructor(){this.time=newObservable((observer)=>{setInterval(()=>{observer.next(newDate().toString());},2000);});}}
What is the option to choose between inline and external template file?
You can store your component's template in one of two places. You can define it inline using the template property, or you can define the template in a separate HTML file and link to it in the component metadata using the @Component decorator's templateUrl property.
The choice between inline and separate HTML is a matter of taste, circumstances, and organization policy. But normally we use inline template for small portion of code and external template file for bigger views. By default, the Angular CLI generates components with a template file. But you can override that with the below command,
Sometimes an app needs to display a view or a portion of a view only under specific circumstances. The Angular *ngIf directive inserts or removes an element based on a truthy/falsy condition. Let's take an example to display a message if the user age is more than 18:
<p*ngIf="user.age > 18">You are not eligible for student pass!</p>
Note: Angular isn't showing and hiding the message. It is adding and removing the paragraph element from the DOM. That improves performance, especially in the larger projects with many data bindings.
What happens if you use script tag inside template?
Angular recognizes the value as unsafe and automatically sanitizes it, which removes the script tag but keeps safe content such as the text content of the script tag. This way it eliminates the risk of script injection attacks. If you still use it then it will be ignored and a warning appears in the browser console.
Let's take an example of innerHtml property binding which causes XSS vulnerability,
exportclassInnerHtmlBindingComponent{// For example, a user/attacker-controlled value from a URL.htmlSnippet='Template <script>alert("0wned")</script> <b>Syntax</b>';}
Interpolation is a special syntax that Angular converts into property binding. It’s a convenient alternative to property binding. It is represented by double curly braces({{}}). The text between the braces is often the name of a component property. Angular replaces that name with the string value of the corresponding component property.
In the example above, Angular evaluates the title and url properties and fills in the blanks, first displaying a bold application title and then a URL.
A template expression produces a value similar to any Javascript expression. Angular executes the expression and assigns it to a property of a binding target; the target might be an HTML element, a component, or a directive. In the property binding, a template expression appears in quotes to the right of the = symbol as in [property]="expression". In interpolation syntax, the template expression is surrounded by double curly braces. For example, in the below interpolation, the template expression is {{username}},
<h3>{{username}}, welcome to Angular</h3>
The below javascript expressions are prohibited in template expression
A template statement responds to an event raised by a binding target such as an element, component, or directive. The template statements appear in quotes to the right of the = symbol like (event)="statement".
Let's take an example of button click event's statement
Pipes are simple functions that use template expressions to accept data as input and transform it into a desired output. For example, let us take a pipe to transform a component's birthday property into a human-friendly date using date pipe.
import{Component}from'@angular/core';
@Component({selector: 'app-birthday',template: `<p>Birthday is {{ birthday | date }}</p>`})exportclassBirthdayComponent{birthday=newDate(1987,6,18);// June 18, 1987}
A pipe can accept any number of optional parameters to fine-tune its output. The parameterized pipe can be created by declaring the pipe name with a colon ( : ) and then the parameter value. If the pipe accepts multiple parameters, separate the values with colons. Let's take a birthday example with a particular format(dd/MM/yyyy):
import{Component}from'@angular/core';
@Component({selector: 'app-birthday',template: `<p>Birthday is {{ birthday | date:'dd/MM/yyyy'}}</p>`// 18/06/1987})exportclassBirthdayComponent{birthday=newDate(1987,6,18);}
Note: The parameter value can be any valid template expression, such as a string literal or a component property.
You can chain pipes together in potentially useful combinations as per the needs. Let's take a birthday property which uses date pipe(along with parameter) and uppercase pipes as below
import{Component}from'@angular/core';
@Component({selector: 'app-birthday',template: `<p>Birthday is {{ birthday | date:'fullDate' | uppercase}} </p>`// THURSDAY, JUNE 18, 1987})exportclassBirthdayComponent{birthday=newDate(1987,6,18);}
Apart from built-in pipes, you can write your own custom pipe with the below key characteristics:
A pipe is a class decorated with pipe metadata @Pipe decorator, which you import from the core Angular library For example,
@Pipe({name: 'myCustomPipe'})
The pipe class implements the PipeTransform interface's transform method that accepts an input value followed by optional parameters and returns the transformed value. The structure of PipeTransform would be as below,
You can create custom reusable pipes for the transformation of existing value. For example, let us create a custom pipe for finding file size based on an extension,
What is the difference between pure and impure pipe?
A pure pipe is only called when Angular detects a change in the value or the parameters passed to a pipe. For example, any changes to a primitive input value (String, Number, Boolean, Symbol) or a changed object reference (Date, Array, Function, Object). An impure pipe is called for every change detection cycle no matter whether the value or parameters changes. i.e, An impure pipe is called often, as often as every keystroke or mouse-move.
Every application has at least one Angular module, the root module that you bootstrap to launch the application is called as bootstrapping module. It is commonly known as AppModule. The default structure of AppModule generated by AngularCLI would be as follows:
import{BrowserModule}from'@angular/platform-browser';import{NgModule}from'@angular/core';import{FormsModule}from'@angular/forms';import{HttpClientModule}from'@angular/common/http';import{AppComponent}from'./app.component';/* the AppModule class with the @NgModule decorator */
@NgModule({declarations: [AppComponent],imports: [BrowserModule,FormsModule,HttpClientModule],providers: [],bootstrap: [AppComponent]})exportclassAppModule{}
Observables are declarative which provide support for passing messages between publishers and subscribers in your application. They are mainly used for event handling, asynchronous programming, and handling multiple values. In this case, 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.
Most of the Front-end applications communicate with backend services over HTTP protocol using either XMLHttpRequest interface or the fetch() API. Angular provides a simplified client HTTP API known as HttpClient which is based on top of XMLHttpRequest interface. This client is avaialble from @angular/common/http package. You can import in your root module as below:
Below are the steps need to be followed for the usage of HttpClient.
Import HttpClient into root module:
import{HttpClientModule}from'@angular/common/http';
@NgModule({imports: [BrowserModule,// import HttpClientModule after BrowserModule.HttpClientModule,],
......
})exportclassAppModule{}
Inject the HttpClient into the application: Let's create a userProfileService(userprofile.service.ts) as an example. It also defines get method of HttpClient:
Create a component for subscribing service: Let's create a component called UserProfileComponent(userprofile.component.ts), which injects UserProfileService and invokes the service method:
The response body doesn't or may not return full response data because sometimes servers also return special headers or status code, which are important for the application workflow. In order to get the full response, you should use observe option from HttpClient:
If the request fails on the server or fails to reach the server due to network issues, then HttpClient will return an error object instead of a successful reponse. In this case, you need to handle in the component by passing error object as a second callback to subscribe() method.
Let's see how it can be handled in the component with an example,
RxJS is a library for composing asynchronous and callback-based code in a functional, reactive style using Observables. Many APIs such as HttpClient produce and consume RxJS Observables and also uses operators for processing observables.
For example, you can import observables and operators for using HttpClient as below,
An Observable instance begins publishing values only when someone subscribes to it. So you need to subscribe by calling the subscribe() method of the instance, passing an observer object to receive the notifications.
Let's take an example of creating and subscribing to a simple observable, with an observer that logs the received message to the console.
// Creates an observable sequence of 5 integers, starting from 1constsource=range(1,5);// Create observer objectconstmyObserver={next: x=>console.log('Observer got a next value: '+x),error: err=>console.error('Observer got an error: '+err),complete: ()=>console.log('Observer got a complete notification'),};// Execute with the observer object and Prints out each itemsource.subscribe(myObserver);// => Observer got a next value: 1// => Observer got a next value: 2// => Observer got a next value: 3// => Observer got a next value: 4// => Observer got a next value: 5// => Observer got a complete notification
An Observable is a unique Object similar to a Promise that can help manage async code. Observables are not part of the JavaScript language so we need to rely on a popular Observable library called RxJS. The observables are created using new keyword.
Let see the simple example of observable,
import{Observable}from'rxjs';constobservable=newObservable(observer=>{setTimeout(()=>{observer.next('Hello from a Observable!');},2000);});
Multi-casting is the practice of broadcasting to a list of multiple subscribers in a single execution.
Let's demonstrate the multi-casting feature:
varsource=Rx.Observable.from([1,2,3]);varsubject=newRx.Subject();varmulticasted=source.multicast(subject);// These are, under the hood, `subject.subscribe({...})`:multicasted.subscribe({next: (v)=>console.log('observerA: '+v)});multicasted.subscribe({next: (v)=>console.log('observerB: '+v)});// This is, under the hood, `s
You can handle errors by specifying an error callback on the observer instead of relying on try/catch, which are ineffective in asynchronous environment.
For example, you can define error callback as below,
myObservable.subscribe({next(num){console.log('Next num: '+num)},error(err){console.log('Received an errror: '+err)}});
What is the shorthand notation for subscribe method?
The subscribe() method can accept callback function definitions in line, for next, error, and complete handlers. It is known as shorthand notation or Subscribe method with positional arguments.
For example, you can define subscribe method as below,
myObservable.subscribe(x=>console.log('Observer got a next value: '+x),err=>console.error('Observer got an error: '+err),()=>console.log('Observer got a complete notification'));
RxJS provides creation functions for the process of creating observables from promises, events, timers and Ajax requests. Let us explain each of them with an example:
Create an observable from a promise
import{from}from'rxjs';// from functionconstdata=from(fetch('/api/endpoint'));//Created from Promisedata.subscribe({next(response){console.log(response);},error(err){console.error('Error: '+err);},complete(){console.log('Completed');}});
Create an observable that creates an AJAX request
import{ajax}from'rxjs/ajax';// ajax functionconstapiData=ajax('/api/data');// Created from AJAX request// Subscribe to create the requestapiData.subscribe(res=>console.log(res.status,res.response));
Create an observable from a counter
import{interval}from'rxjs';// interval functionconstsecondsCounter=interval(1000);// Created from Counter valuesecondsCounter.subscribe(n=>console.log(`Counter value: ${n}`));
Create an observable from an event
import{fromEvent}from'rxjs';constel=document.getElementById('custom-element');constmouseMoves=fromEvent(el,'mousemove');constsubscription=mouseMoves.subscribe((e: MouseEvent)=>{console.log(`Coordnitaes of mouse pointer: ${e.clientX} * ${e.clientY}`);});
What will happen if you do not supply handler for the observer?
Usually, an observer object can define any combination of next, error, and complete notification type handlers. If you don't supply a handler for a notification type, the observer just ignores notifications of that type.
Angular elements are Angular components packaged as custom elements (a web standard for defining new HTML elements in a framework-agnostic way). Angular Elements host an Angular component, providing a bridge between the data and the logic defined in the component and the standard DOM APIs, thus, providing a way to use Angular components in non-Angular environments.
Since Angular elements are packaged as custom elements the browser support of angular elements is same as custom elements support.
This feature is is currently supported natively in a number of browsers and pending for other browsers.
Browser
Angular Element Support
Chrome
Natively supported
Opera
Natively supported
Safari
Natively supported
Firefox
Natively supported from 63 version onwards. You need to enable dom.webcomponents.enabled and dom.webcomponents.customelements.enabled in older browsers
Custom elements (or Web Components) are a Web Platform feature which extends HTML by allowing you to define a tag whose content is created and controlled by JavaScript code. The browser maintains a CustomElementRegistry of defined custom elements, which maps an instantiable JavaScript class to an HTML tag. Currently this feature is supported by Chrome, Firefox, Opera, and Safari, and available in other browsers through polyfills.
No, custom elements bootstrap (or start) automatically when they are added to the DOM, and are automatically destroyed when removed from the DOM. Once a custom element is added to the DOM for any page, it looks and behaves like any other HTML element, and does not require any special knowledge of Angular.
Below are the steps in an order about custom elements functionality,
App registers custom element with browser: Use the createCustomElement() function to convert a component into a class that can be registered with the browser as a custom element.
App adds custom element to DOM: Add custom element just like a built-in HTML element directly into the DOM.
Browser instantiate component based class: Browser creates an instance of the registered class and adds it to the DOM.
Instance provides content with data binding and change detection: The content with in template is rendered using the component and DOM data. The flow chart of the custom elements functionality would be as follows,
Transforming components to custom elements involves two major steps,
Build custom element class: Angular provides the createCustomElement() function for converting an Angular component (along with its dependencies) to a custom element. The conversion process implements NgElementConstructor interface, and creates a constructor class which is used to produce a self-bootstrapping instance of Angular component.
Register element class with browser: It uses customElements.define() JS function, to register the configured constructor and its associated custom-element tag with the browser's CustomElementRegistry. When the browser encounters the tag for the registered element, it uses the constructor to create a custom-element instance.
What are the mapping rules between Angular component and custom element?
The Component properties and logic maps directly into HTML attributes and the browser's event system. Let us describe them in two steps,
The createCustomElement() API parses the component input properties with corresponding attributes for the custom element. For example, component @Input('myInputProp') converted as custom element attribute my-input-prop.
The Component outputs are dispatched as HTML Custom Events, with the name of the custom event matching the output name. For example, component @Output() valueChanged = new EventEmitter() converted as custom element with dispatch event as "valueChanged".
After applying types typescript validates input value and their types,
const container = document.createElement('my-container') as NgElement & WithProperties<{message: string}>;
container.message = 'Welcome to Angular elements!';
container.message = true; // <-- ERROR: TypeScript knows this should be a string.
container.greet = 'News'; // <-- ERROR: TypeScript knows there is no `greet` property on `container`.
Dynamic components are the components in which the component's location in the application is not defined at build time i.e. they are not used in any angular template. Instead, the component is instantiated and placed in the application at runtime.
You can use CLI command ng generate directive to create the directive class file. It creates the source file(src/app/components/directivename.directive.ts), the respective test file .spec.ts and declare the directive class file in root module.
Let's take simple highlighter behavior as a example directive for DOM element. You can create and apply the attribute directive using below step:
Create HighlightDirective class with the file name src/app/highlight.directive.ts. In this file, we need to import Directive from core library to apply the metadata and ElementRef in the directive's constructor to inject a reference to the host DOM element ,
Angular Router is a mechanism in which navigation happens from one view to the next as users perform application tasks. It borrows the concepts or model of browser's application navigation. It enables developers to build Single Page Applications with multiple views and allow navigation between these views.
The routing application should add element to the index.html as the first child in the tag in order to indicate how to compose navigation URLs. If app folder is the application root then you can set the href value as below
The Angular Router which represents a particular component view for a given URL is not part of Angular Core. It is available in library named @angular/router to import required router components. For example, we import them in app module as below,
The RouterOutlet is a directive from the router library and it acts as a placeholder that marks the spot in the template where the router should display the components for that outlet. Router outlet is used like a component,
<router-outlet></router-outlet><!-- Routed components go here -->
The RouterLink is a directive on the anchor tags give the router control over those elements. Since the navigation paths are fixed, you can assign string values to router-link directive as below,
<h1>Angular Router</h1><nav><arouterLink="/todosList" >List of todos</a><arouterLink="/completed" >Completed todos</a></nav><router-outlet></router-outlet>
RouterLinkActive is a directive that toggles css classes for active RouterLink bindings based on the current RouterState. i.e, The Router will add CSS classes when this link is active and remove when the link is inactive. For example, you can add them to RouterLinks as below.
<h1>Angular Router</h1><nav><arouterLink="/todosList" routerLinkActive="active">List of todos</a><arouterLink="/completed" routerLinkActive="active">Completed todos</a></nav><router-outlet></router-outlet>
RouterState is a tree of activated routes. Every node in this tree knows about the "consumed" URL segments, the extracted parameters, and the resolved data. You can access the current RouterState from anywhere in the application using the Router service and the routerState property.
ActivatedRoute contains the information about a route associated with a component loaded in an outlet. It can also be used to traverse the router state tree. The ActivatedRoute will be injected as a router service to access the information. In the below example, you can access route path and parameters,
@Component({...})classMyComponent{constructor(route: ActivatedRoute){constid: Observable<string> = route.params.pipe(map(p =>p.id));consturl: Observable<string> = route.url.pipe(map(segments =>segments.join('')));// route.data includes both `data` and `resolve`constuser=route.data.pipe(map(d=>d.user));}}
A router must be configured with a list of route definitions. You configures the router with routes via the RouterModule.forRoot() method, and adds the result to the AppModule's imports array.
If the URL doesn't match any predefined routes then it causes the router to throw an error and crash the app. In this case, you can use wildcard route. A wildcard route has a path consisting of two asterisks to match every URL.
For example, you can define PageNotFoundComponent for wildcard route as below
No, the Routing Module is a design choice. You can skip routing Module (for example, AppRoutingModule) when the configuration is simple and merge the routing configuration directly into the companion module (for example, AppModule). But it is recommended when the configuration is complex and includes specialized guard and resolver services.
Angular Universal is a server-side rendering module for Angular applications in various scenarios. This is a community driven project and available under @angular/platform-server package. Recently Angular Universal is integrated with Angular CLI.
Just-in-Time (JIT) is a type of compilation that compiles your app in the browser at runtime. JIT compilation was the default until Angular 8, now default is AOT. When you run the ng build (build only) or ng serve (build and serve locally) CLI commands, the type of compilation (JIT or AOT) depends on the value of the aot property in your build configuration specified in angular.json. By default, aot is set to true.
Ahead-of-Time (AOT) is a type of compilation that compiles your app at build time. This is the default starting in Angular 9. When you run the ng build (build only) or ng serve (build and serve locally) CLI commands, the type of compilation (JIT or AOT) depends on the value of the aot property in your build configuration specified in angular.json. By default, aot is set to true.
The Angular components and templates cannot be understood by the browser directly. Due to that Angular applications require a compilation process before they can run in a browser. For example, In AOT compilation, both Angular HTML and TypeScript code converted into efficient JavaScript code during the build phase before browser runs it.
Faster rendering: The browser downloads a pre-compiled version of the application. So it can render the application immediately without compiling the app.
Fewer asynchronous requests: It inlines external HTML templates and CSS style sheets within the application javascript which eliminates separate ajax requests.
Smaller Angular framework download size: Doesn't require downloading the Angular compiler. Hence it dramatically reduces the application payload.
Detect template errors earlier: Detects and reports template binding errors during the build step itself
Better security: It compiles HTML templates and components into JavaScript. So there won't be any injection attacks.
If you still use arrow function, it generates an error node in place of the function. When the compiler later interprets this node, it reports an error to turn the arrow function into an exported function. Note: From Angular5 onwards, the compiler automatically performs this rewriting while emitting the .js file.
The metadata.json file can be treated as a diagram of the overall structure of a decorator's metadata, represented as an abstract syntax tree(AST). During the analysis phase, the AOT collector scan the metadata recorded in the Angular decorators and outputs metadata information in .metadata.json files, one per .d.ts file.
Can I use any javascript feature for expression syntax in AOT?
No, the AOT collector understands a subset of (or limited) JavaScript features. If an expression uses unsupported syntax, the collector writes an error node to the .metadata.json file. Later point of time, the compiler reports an error if it needs that piece of metadata to generate the application code.
The compiler can only resolve references to exported symbols in the metadata. Where as some of the non-exported members are folded while generating the code. i.e Folding is a process in which the collector evaluate an expression during collection and record the result in the .metadata.json instead of the original expression. For example, the compiler couldn't refer selector reference because it is not exported
The AOT compiler supports macros in the form of functions or static methods that return an expression in a single return expression. For example, let us take a below macro function,
Below are some of the errors encountered in metadata,
Expression form not supported: Some of the language features outside of the compiler's restricted expression syntax used in angular metadata can produce this error. Let's see some of these examples,
1.exportclassUser{ ... }constprop=typeofUser;// typeof is not valid in metadata2.{provide: 'token',useValue: {[prop]: 'value'}};// bracket notation is not valid in metadata
Reference to a local (non-exported) symbol: The compiler encountered a referenced to a locally defined symbol that either wasn't exported or wasn't initialized. Let's take example of this error,
Function calls are not supported: The compiler does not currently support function expressions or lambda functions. For example, you cannot set a provider's useFactory to an anonymous function or arrow function as below.
Destructured variable or constant not supported: The compiler does not support references to variables assigned by destructuring. For example, you cannot write something like this:
import{user}from'./user';// destructured assignment to name and ageconst{name, age}=user;
... //metadata
providers: [{provide: Name,useValue: name},{provide: Age,useValue: age},]
You can fix this by non-destructured values
import { user } from './user';
... //metadata
providers: [
{provide: Name, useValue: user.name},
{provide: Age, useValue: user.age},
]
Metadata rewriting is the process in which the compiler converts the expression initializing the fields such as useClass, useValue, useFactory, and data into an exported variable, which replaces the expression. Remember that the compiler does this rewriting during the emit of the .js file but not in definition files( .d.ts file).
Angular Compiler supports configuration inheritance through extends in the tsconfig.json on angularCompilerOptions. i.e, The configuration from the base file(for example, tsconfig.base.json) are loaded first, then overridden by those in the inheriting config file.
How do you specify angular template compiler options?
The angular template compiler options are specified as members of the angularCompilerOptions object in the tsconfig.json file. These options will be specified adjecent to typescript compiler options.
You can enable binding expression validation explicitly by adding the compiler option fullTemplateTypeCheck in the "angularCompilerOptions" of the project's tsconfig.json. It produces error messages when a type error is detected in a template binding expression.
You can disable binding expression type checking using $any() type cast function(by surrounding the expression). In the following example, the error Property contacts does not exist is suppressed by casting user to the any type.
template:
'{{ $any(user).contacts.email }}'
The $any() cast function also works with this to allow access to undeclared members of the component.
You can use the non-null type assertion operator to suppress the Object is possibly 'undefined' error. In the following example, the user and contact properties are always set together, implying that contact is always non-null if user is non-null. The error is suppressed in the example by using contact!.email.
The expression used in an ngIf directive is used to narrow type unions in the Angular template compiler similar to if expression in typescript. So *ngIf allows the typeScript compiler to infer that the data used in the binding expression will never be undefined.
A Zone is an execution context that persists across async tasks. Angular relies on zone.js to run Angular's change detection processes when native JavaScript operations raise events
The commonly-needed services, pipes, and directives provided by @angular/common module. Apart from these HttpClientModule is available under @angular/common/http.
Codelyzer provides set of tslint rules for static code analysis of Angular TypeScript projects. You can run the static code analyzer over web apps, NativeScript, Ionic etc. Angular CLI has support for this and it can be use as below,
Angular's animation system is built on CSS functionality in order to animate any property that the browser considers animatable. These properties includes positions, sizes, transforms, colors, borders etc. The Angular modules for animations are @angular/animations and @angular/platform-browser and these dependencies are automatically added to your project when you create a project using Angular CLI.
You need to follow below steps to implement animation in your angular project,
Enabling the animations module: Import BrowserAnimationsModule to add animation capabilities into your Angular root application module(for example, src/app/app.module.ts).
Importing animation functions into component files: Import required animation functions from @angular/animations in component files(for example, src/app/app.component.ts).
Adding the animation metadata property: add a metadata property called animations: within the @Component() decorator in component files(for example, src/app/app.component.ts)
@Component({selector: 'app-root',templateUrl: 'app.component.html',styleUrls: ['app.component.css'],animations: [// animation triggers go here]})
Angular's state() function is used to define different states to call at the end of each transition. This function takes two arguments: a unique name like open or closed and a style() function.
The style function is used to define a set of styles to associate with a given state name. You need to use it along with state() function to set CSS style attributes. For example, in the close state, the button has a height of 100 pixels, an opacity of 0.8, and a background color of green.
The animation transition function is used to specify the changes that occur between one state and another over a period of time. It accepts two arguments: the first argument accepts an expression that defines the direction between two transition states, and the second argument accepts an animate() function.
Let's take an example state transition from open to closed with an half second transition between states.
A service worker is a script that runs in the web browser and manages caching for an application. Starting from 5.0.0 version, Angular ships with a service worker implementation. Angular service worker is designed to optimize the end user experience of using an application over a slow or unreliable network connection, while also minimizing the risks of serving outdated content.
What are the differences between AngularJS and Angular with respect to dependency injection?
Dependency injection is a common component in both AngularJS and Angular, but there are some key differences between the two frameworks in how it actually works.
AngularJS
Angular
Dependency injection tokens are always strings
Tokens can have different types. They are often classes and sometimes can be strings.
There is exactly one injector even though it is a multi-module applications
There is a tree hierarchy of injectors, with a root injector and an additional injector for each component.
Yes, it is a recommended configuration. Also, AOT compilation with Ivy is faster. So you need set the default build options(with in angular.json) for your project to always use AOT compilation.
The Angular Language Service is a way to get completions, errors, hints, and navigation inside your Angular templates whether they are external in an HTML file or embedded in annotations/decorators in a string. It has the ability to autodetect that you are opening an Angular file, reads your tsconfig.json file, finds all the templates you have in your application, and then provides all the language services.
Is there any editor support for Angular Language Service?
Yes, Angular Language Service is currently available for Visual Studio Code and WebStorm IDEs. You need to install angular language service using an extension and devDependency respectively. In sublime editor, you need to install typescript which has has a language service plugin model.
Explain the features provided by Angular Language Service?
Basically there are 3 main features provided by Angular Language Service,
Autocompletion: Autocompletion can speed up your development time by providing you with contextual possibilities and hints as you type with in an interpolation and elements.
Error checking: It can also warn you of mistakes in your code.
Navigation: Navigation allows you to hover a component, directive, module and then click and press F12 to go directly to its definition.
You can add web worker anywhere in your application. For example, If the file that contains your expensive computation is src/app/app.component.ts, you can add a Web Worker using ng generate web-worker app command which will create src/app/app.worker.ts web worker file. This command will perform below actions,
Configure your project to use Web Workers
Adds app.worker.ts to receive messages
addEventListener('message',({ data })=>{constresponse=`worker response to ${data}`;postMessage(response);});
The component app.component.ts file updated with web worker file
if(typeofWorker!=='undefined'){// Create a newconstworker=newWorker('./app.worker',{type: 'module'});worker.onmessage=({ data })=>{console.log('page got message: $\{data\}');};worker.postMessage('hello');}else{// Web Workers are not supported in this environment.}
Note: You may need to refactor your initial scaffolding web worker code for sending messages to and from.
You need to remember two important things when using Web Workers in Angular projects,
Some environments or platforms(like @angular/platform-server) used in Server-side Rendering, don't support Web Workers. In this case you need to provide a fallback mechanism to perform the computations to work in this environments.
Running Angular in web worker using @angular/platform-webworker is not yet supported in Angular CLI.
In Angular8, the CLI Builder API is stable and available to developers who want to customize the Angular CLI by adding or modifying commands. For example, you could supply a builder to perform an entirely new task, or to change which third-party tool is used by an existing command.
A builder function is a function that uses the Architect API to perform a complex process such as "build" or "test". The builder code is defined in an npm package. For example, BrowserBuilder runs a webpack build for a browser target and KarmaBuilder starts the Karma server and runs a webpack build for unit tests.
The Angular CLI command ng run is used to invoke a builder with a specific target configuration. The workspace configuration file, angular.json, contains default configurations for built-in builders.
An App shell is a way to render a portion of your application via a route at build time. This is useful to first paint of your application that appears quickly because the browser can render static HTML and CSS without the need to initialize JavaScript. You can achieve this using Angular CLI which generates an app shell for running server-side of your app.
Angular uses capitalization conventions to distinguish the names of various types. Angular follows the list of the below case types.
camelCase : Symbols, properties, methods, pipe names, non-component directive selectors, constants uses lowercase on the first letter of the item. For example, "selectedUser"
UpperCamelCase (or PascalCase): Class names, including classes that define components, interfaces, NgModules, directives, and pipes uses uppercase on the first letter of the item.
dash-case (or "kebab-case"): The descriptive part of file names, component selectors uses dashes between the words. For example, "app-user-list".
UPPER_UNDERSCORE_CASE: All constants uses capital letters connected with underscores. For example, "NUMBER_OF_USERS".
A class decorator is a decorator that appears immediately before a class definition, which declares the class to be of the given type, and provides metadata suitable to the type
The following list of decorators comes under class decorators,
The class field decorators are the statements declared immediately before a field in a class definition that defines the type of that field. Some of the examples are: @input and @output,
Declarable is a class type that you can add to the declarations list of an NgModule. The class types such as components, directives, and pipes comes can be declared in the module. The structure of declarations would be,
A DI token is a lookup token associated with a dependency provider in dependency injection system. The injector maintains an internal token-provider map that it references when asked for a dependency and the DI token is the key to the map. Let's take example of DI Token usage,
A domain-specific language (DSL) is a computer language specialized to a particular application domain. Angular has its own Domain Specific Language (DSL) which allows us to write Angular specific html-like syntax on top of normal html. It has its own compiler that compiles this syntax to html that the browser can understand. This DSL is defined in NgModules such as animations, forms, and routing and navigation.
Basically you will see 3 main syntax in Angular DSL.
(): Used for Output and DOM events.
[]: Used for Input and specific DOM element attributes.
*: Structural directives(*ngFor or *ngIf) will affect/change the DOM structure.
An RxJS Subject is a special type of Observable that allows values to be multicasted to many Observers. While plain Observables are unicast (each subscribed Observer owns an independent execution of the Observable), Subjects are multicast.
A Subject is like an Observable, but can multicast to many Observers. Subjects are like EventEmitters: they maintain a registry of many listeners.
Bazel is a powerful build tool developed and massively used by Google and it can keep track of the dependencies between different packages and build targets. In Angular8, you can build your CLI application with Bazel. Note: The Angular framework itself is built with Bazel.
Sometimes you may want to bypass the Angular CLI builder and run Bazel directly using Bazel CLI. You can install it globally using @bazel/bazel npm package. i.e, Bazel CLI is available under @bazel/bazel package. After you can apply the below common commands,
bazel build [targets] // Compile the default output artifacts of the given targets.
bazel test [targets] // Run the tests with *_test targets found in the pattern.
bazel run [target]: Compile the program represented by target and then run it.
A platform is the context in which an Angular application runs. The most common platform for Angular applications is a web browser, but it can also be an operating system for a mobile device, or a web server. The runtime-platform is provided by the @angular/platform-* packages and these packages allow applications that make use of @angular/core and @angular/common to execute in different environments. i.e, Angular can be used as platform-independent framework in different environments, For example,
While running in the browser, it uses platform-browser package.
When SSR(server-side rendering ) is used, it uses platform-server package for providing web server implementation.
If multiple modules imports the same module then angular evaluates it only once (When it encounters the module first time). It follows this condition even the module appears at any level in a hierarchy of imported NgModules.
In Angular7, you can subscribe to router to detect the changes. The subscription for router events would be as below,
this.router.events.subscribe((event: Event)=>{})
Let's take a simple component to detect router changes
import{Component}from'@angular/core';import{Router,Event,NavigationStart,NavigationEnd,NavigationError}from'@angular/router';
@Component({selector: 'app-root',template: `<router-outlet></router-outlet>`})exportclassAppComponent{constructor(privaterouter: Router){this.router.events.subscribe((event: Event)=>{if(eventinstanceofNavigationStart){// Show loading indicator and perform an action}if(eventinstanceofNavigationEnd){// Hide loading indicator and perform an action}if(eventinstanceofNavigationError){// Hide loading indicator and perform an actionconsole.log(event.error);// It logs an error for debugging}});}}
You can directly pass object map for http client or create HttpHeaders class to supply the headers.
constructor(private_http: HttpClient){}this._http.get('someUrl',{headers: {'header1':'value1','header2':'value2'}});(or)letheaders=newHttpHeaders().set('header1',headerValue1);// create header objectheaders=headers.append('header2',headerValue2);// add a new header, creating a new objectheaders=headers.append('header3',headerValue3);// add another headerletparams=newHttpParams().set('param1',value1);// create params objectparams=params.append('param2',value2);// add a new param, creating a new objectparams=params.append('param3',value3);// add another paramreturnthis._http.get<any[]>('someUrl',{headers: headers,params: params})
What is the purpose of differential loading in CLI?
From Angular8 release onwards, the applications are built using differential loading strategy from CLI to build two separate bundles as part of your deployed application.
The first build contains ES2015 syntax which takes the advantage of built-in support in modern browsers, ships less polyfills, and results in a smaller bundle size.
The second build contains old ES5 syntax to support older browsers with all necessary polyfills. But this results in a larger bundle size.
Note: This strategy is used to support multiple browsers but it only load the code that the browser needs.
Yes, Angular 8 supports dynamic imports in router configuration. i.e, You can use the import statement for lazy loading the module using loadChildren method and it will be understood by the IDEs(VSCode and WebStorm), webpack, etc. Previously, you have been written as below to lazily load the feature module. By mistake, if you have typo in the module name it still accepts the string and throws an error during build time.
Lazy loading is one of the most useful concepts of Angular Routing. It helps us to download the web pages in chunks instead of downloading everything in a big bundle. It is used for lazy loading by asynchronously loading the feature module for routing whenever required using the property loadChildren. Let's load both Customer and Order feature modules lazily as below,
Angular 8.0 release introduces Workspace APIs to make it easier for developers to read and modify the angular.json file instead of manually modifying it. Currently, the only supported storage3 format is the JSON-based format used by the Angular CLI. You can enable or add optimization option for build target as below,
import{NodeJsSyncHost}from'@angular-devkit/core/node';import{workspaces}from'@angular-devkit/core';asyncfunctionaddBuildTargetOption(){consthost=workspaces.createWorkspaceHost(newNodeJsSyncHost());constworkspace=awaitworkspaces.readWorkspace('path/to/workspace/directory/',host);constproject=workspace.projects.get('my-app');if(!project){thrownewError('my-app does not exist');}constbuildTarget=project.targets.get('build');if(!buildTarget){thrownewError('build target does not exist');}buildTarget.options.optimization=true;awaitworkspaces.writeWorkspace(workspace,host);}addBuildTargetOption();
The Angular upgrade is quite easier using Angular CLI ng update command as mentioned below. For example, if you upgrade from Angular 7 to 8 then your lazy loaded route imports will be migrated to the new import syntax automatically.
Angular Material is a collection of Material Design components for Angular framework following the Material Design spec. You can apply Material Design very easily using Angular Material. The installation can be done through npm or yarn,
If you are using $location service in your old AngularJS application, now you can use LocationUpgradeModule(unified location service) which puts the responsibilities of $location service to Location service in Angular. Let's add this module to AppModule as below,
// Other imports ...import{LocationUpgradeModule}from'@angular/common/upgrade';
@NgModule({imports: [// Other NgModule imports...LocationUpgradeModule.config()]})exportclassAppModule{}
NgUpgrade is a library put together by the Angular team, which you can use in your applications to mix and match AngularJS and Angular components and bridge the AngularJS and Angular dependency injection systems.
Angular CLI downloads and install everything needed with the Jasmine Test framework. You just need to run ng test to see the test results. By default this command builds the app in watch mode, and launches the Karma test runner. The output of test results would be as below,
10% building modules 1/1 modules 0 active
...INFO [karma]: Karma v1.7.1 server started at http://0.0.0.0:9876/
...INFO [launcher]: Launching browser Chrome ...
...INFO [launcher]: Starting browser Chrome
...INFO [Chrome ...]: Connected on socket ...
Chrome ...: Executed 3 of 3 SUCCESS (0.135 secs / 0.205 secs)
Note: A chrome browser also opens and displays the test output in the "Jasmine HTML Reporter".
The Angular CLI provides support for polyfills officially. When you create a new project with the ng new command, a src/polyfills.ts configuration file is created as part of your project folder. This file includes the mandatory and many of the optional polyfills as JavaScript import statements. Let's categorize the polyfills,
Mandatory polyfills: These are installed automatically when you create your project with ng new command and the respective import statements enabled in 'src/polyfills.ts' file.
Optional polyfills: You need to install its npm package and then create import statement in 'src/polyfills.ts' file. For example, first you need to install below npm package for adding web animations (optional) polyfill. bash npm install --save web-animations-js and create import statement in polyfill file. javascript import 'web-animations-js';
What are the ways to trigger change detection in Angular?
You can inject either ApplicationRef or NgZone, or ChangeDetectorRef into your component and apply below specific methods to trigger change detection in Angular. i.e, There are 3 possible ways,
ApplicationRef.tick(): Invoke this method to explicitly process change detection and its side-effects. It check the full component tree.
NgZone.run(callback): It evaluate the callback function inside the Angular zone.
ChangeDetectorRef.detectChanges(): It detects only the components and it's children.
What are the differences of various versions of Angular?
There are different versions of Angular framework. Let's see the features of all the various versions,
Angular 1:
Angular 1 (AngularJS) is the first angular framework released in the year 2010.
AngularJS is not built for mobile devices.
It is based on controllers with MVC architecture.
Angular 2:
Angular 2 was released in the year 2016. Angular 2 is a complete rewrite of Angular1 version.
The performance issues that Angular 1 version had has been addressed in Angular 2 version.
Angular 2 is built from scratch for mobile devices unlike Angular 1 version.
Angular 2 is components based.
Angular 3:
The following are the different package versions in Angular 2:
@angular/core v2.3.0
@angular/compiler v2.3.0
@angular/http v2.3.0
@angular/router v3.3.0
The router package is already versioned 3 so to avoid confusion switched to Angular 4 version and skipped 3 version.
Angular 4:
The compiler generated code file size in AOT mode is very much reduced.
With Angular 4 the production bundles size is reduced by hundreds of KB’s.
Animation features are removed from angular/core and formed as a separate package.
Supports Typescript 2.1 and 2.2.
Angular Universal
New HttpClient
Angular 5:
Angular 5 makes angular faster. It improved the loading time and execution time.
Shipped with new build optimizer.
Supports Typescript 2.5.
Service Worker
Angular 6:
It is released in May 2018.
Includes Angular Command Line Interface (CLI), Component Development KIT (CDK), Angular Material Package, Angular Elements.
Service Worker bug fixes.
i18n
Experimental mode for Ivy.
RxJS 6.0
Tree Shaking
Angular 7:
It is released in October 2018.
TypeScript 3.1
RxJS 6.3
New Angular CLI
CLI Prompts capability provide an ability to ask questions to the user before they run. It is like interactive dialog between the user and the CLI
With the improved CLI Prompts capability, it helps developers to make the decision. New ng commands ask users for routing and CSS styles types(SCSS) and ng add @angular/material asks for themes and gestures or animations.
What is the reason to deprecate Web Tracing Framework?
Angular has supported the integration with the Web Tracing Framework (WTF) for the purpose of performance testing. Since it is not well maintained and failed in majority of the applications, the support is deprecated in latest releases.
What is the reason to deprecate web worker packages?
Both @angular/platform-webworker and @angular/platform-webworker-dynamic are officially deprecated, the Angular team realized it's not good practice to run the Angular application on Web worker
It's a scaffolding library that defines how to generate or transform a programming project by creating, modifying, refactoring, or moving files and code. It defines rules that operate on a virtual file system called a tree.
Schematics come with their own command-line tool known as Schematics CLI. It is used to install the schematics executable, which you can use to create a new schematics collection with an initial named schematic. The collection folder is a workspace for schematics. You can also use the schematics command to add a new schematic to an existing collection, or extend an existing schematic. You can install Schematic CLI globally as below,
What is Angular security model for preventing XSS attacks?
Angular treats all values as untrusted by default. i.e, Angular sanitizes and escapes untrusted values When a value is inserted into the DOM from a template, via property, attribute, style, class binding, or interpolation.
What is the role of template compiler for prevention of XSS attacks?
The offline template compiler prevents vulnerabilities caused by template injection, and greatly improves application performance. So it is recommended to use offline template compiler in production deployments without dynamically generating any template.
Sanitization is the inspection of an untrusted value, turning it into a value that's safe to insert into the DOM. Yes, Angular suppports sanitization. It sanitizes untrusted values for HTML, styles, and URLs but sanitizing resource URLs isn't possible because they contain arbitrary code.
The innerHtml is a property of HTML-Elements, which allows you to set it's html-content programmatically. Let's display the below html code snippet in a <div> tag as below using innerHTML binding,
<div[innerHTML]="htmlSnippet"></div>
and define the htmlSnippet property from any component
What is the difference between interpolated content and innerHTML?
The main difference between interpolated and innerHTML code is the behavior of code interpreted. Interpolated content is always escaped i.e, HTML isn't interpreted and the browser displays angle brackets in the element's text content. Where as in innerHTML binding, the content is interpreted i.e, the browser will convert < and > characters as HTMLEntities. For example, the usage in template would be as below,
<p>Interpolated value:</p><div>{{htmlSnippet}}</div><p>Binding of innerHTML:</p><div[innerHTML]="htmlSnippet"></div>
Sometimes the applications genuinely need to include executable code such as displaying <iframe> from an URL. In this case, you need to prevent automatic sanitization in Angular by saying that you inspected a value, checked how it was generated, and made sure it will always be secure. Basically it involves 2 steps,
Inject DomSanitizer: You can inject DomSanitizer in component as parameter in constructor
Mark the trusted value by calling some of the below methods
bypassSecurityTrustHtml
bypassSecurityTrustScript
bypassSecurityTrustStyle
bypassSecurityTrustUrl
bypassSecurityTrustResourceUrl
For example,The usage of dangerous url to trusted url would be as below,
Is safe to use direct DOM API methods in terms of security?
No,the built-in browser DOM APIs or methods don't automatically protect you from security vulnerabilities. In this case it is recommended to use Angular templates instead of directly interacting with DOM. If it is unavoidable then use the built-in Angular sanitization functions.
How do you support server side XSS protection in Angular application?
The server-side XSS protection is supported in an angular application by using a templating language that automatically escapes values to prevent XSS vulnerabilities on the server. But don't use a templating language to generate Angular templates on the server side which creates a high risk of introducing template-injection vulnerabilities.
Angular has built-in support for preventing http level vulnerabilities such as as cross-site request forgery (CSRF or XSRF) and cross-site script inclusion (XSSI). Even though these vulnerabilities need to be mitigated on server-side, Angular provides helpers to make the integration easier on the client side.
HttpClient supports a token mechanism used to prevent XSRF attacks
HttpClient library recognizes the convention of prefixed JSON responses(which non-executable js code with ")]}',\n" characters) and automatically strips the string ")]}',\n" from all responses before further parsing
Http Interceptors are part of @angular/common/http, which inspect and transform HTTP requests from your application to the server and vice-versa on HTTP responses. These interceptors can perform a variety of implicit tasks, from authentication to logging.
The syntax of HttpInterceptor interface looks like as below,
The interceptors will be called in the order in which they were provided. i.e, MyFirstInterceptor will be called first in the above interceptors configuration.
How can I use interceptor for an entire application?
You can use same instance of HttpInterceptors for the entire app by importing the HttpClientModule only in your AppModule, and add the interceptors to the root application injector. For example, let's define a class that is injectable in root application.
By default, Angular only contains locale data for en-US which is English as spoken in the United States of America . But if you want to set to another locale, you must import locale data for that new locale. After that you can register using registerLocaleData method and the syntax of this method looks like below,
The i18n template translation process has four phases:
Mark static text messages in your component templates for translation: You can place i18n on every element tag whose fixed text is to be translated. For example, you need i18n attribue for heading as below,
<h1i18n>Hello i18n!</h1>
Create a translation file: Use the Angular CLI xi18n command to extract the marked text into an industry-standard translation source file. i.e, Open terminal window at the root of the app project and run the CLI command xi18n.
ng xi18n
The above command creates a file named messages.xlf in your project's root directory.
Note: You can supply command options to change the format, the name, the location, and the source locale of the extracted file.
Edit the generated translation file: Translate the extracted text into the target language. In this step, create a localization folder (such as locale)under root directory(src) and then create target language translation file by copying and renaming the default messages.xlf file. You need to copy source text node and provide the translation under target tag. For example, create the translation file(messages.de.xlf) for German language
<trans-unitid="greetingHeader"datatype="html"><source>Hello i18n!</source><target>Hallo i18n !</target><notepriority="1"from="description">A welcome header for this sample</note><notepriority="1"from="meaning">welcome message</note></trans-unit>
Merge the completed translation file into the app: You need to use Angular CLI build command to compile the app, choosing a locale-specific configuration, or specifying the following command options.
The Angular i18n attribute marks translatable content. It is a custom attribute, recognized by Angular tools and compilers. The compiler removes it after translation.
Note: Remember that i18n is not an Angular directive.
When you change the translatable text, the Angular extractor tool generates a new id for that translation unit. Because of this behavior, you must then update the translation file with the new id every time.
For example, the translation file messages.de.xlf.html has generated trans-unit for some text message as below
You need to define custom ids as unique. If you use the same id for two different text messages then only the first one is extracted. But its translation is used in place of both original text messages.
For example, let's define same custom id myCustomId for two messages,
Yes, you can achieve using <ng-container> attribute. Normally you need to wrap a text content with i18n attribute for the translation. But if you don't want to create a new DOM element just for the sake of translation, you can wrap the text in an element.
<ng-containeri18n>I'm not using any DOM element for translation</ng-container>
Remember that <ng-container> is transformed into an html comment
You can translate attributes by attaching i18n-x attribute where x is the name of the attribute to translate. For example, you can translate image title attribute as below,
ICU expression is is similar to the plural expressions except that you choose among alternative translations based on a string value instead of a number. Here you define those string values.
Let's take component binding with residenceStatus property which has "citizen", "permanent resident" and "foreigner" possible values and the message maps those values to the appropriate translations.
<spani18n>The person is {residenceStatus,select,citizen{citizen} permanent resident {permanentResident} foreigner {foreigner}}</span>
By default, When translation is missing, it generates a warning message such as "Missing translation for message 'somekey'". But you can configure with a different level of message in Angular compiler as below,
Error: It throws an error. If you are using AOT compilation, the build will fail. But if you are using JIT compilation, the app will fail to load.
Warning (default): It shows a 'Missing translation' warning in the console or shell.
Ignore: It doesn't do anything.
If you use AOT compiler then you need to perform changes in configurations section of your Angular CLI configuration file, angular.json.
If you use the JIT compiler, specify the warning level in the compiler config at bootstrap by adding the 'MissingTranslationStrategy' property as below,
How do you provide build configuration for multiple locales?
You can provide build configuration such as translation file path, name, format and application url in configuration settings of Angular.json file. For example, the German version of your application configured the build as follows,
An Angular library is an Angular project that differs from an app in that it cannot run on its own. It must be imported and used in an app. For example, you can import or add service worker library to an Angular application which turns an application into a Progressive Web App (PWA).
Note: You can create own third party library and publish it as npm package to be used in an Application.
The AOT compiler is part of a build process that produces a small, fast, ready-to-run application package, typically for production. It converts your Angular HTML and TypeScript code into efficient JavaScript code during the build phase before the browser downloads and runs that code.
How do you select an element in component template?
You can control any DOM element via ElementRef by injecting it into your component's constructor. i.e, The component should have constructor with ElementRef parameter,
TestBed is an api for writing unit tests for Angular applications and it's libraries. Even though We still write our tests in Jasmine and run using Karma, this API provides an easier way to create components, handle injection, test asynchronous behaviour and interact with our application.
Protractor is an end-to-end test framework for Angular and AngularJS applications. It runs tests against your application running in a real browser, interacting with it as a user would.
Collection is a set of related schematics collected in an npm package. For example, @schematics/angular collection is used in Angular CLI to apply transforms to a web-app project. You can create your own schematic collection for customizing angular projects.
You can create your own schematic collections to integrate your library with the Angular CLI. These collections are classified as 3 main schematics,
Add schematics: These schematics are used to install library in an Angular workspace using ng add command. For example, @angular/material schematic tells the add command to install and set up Angular Material and theming.
Generate schematics: These schematics are used to modify projects, add configurations and scripts, and scaffold artifacts in library using ng generate command. For example, @angular/material generation schematic supplies generation schematics for the UI components. Let's say the table component is generated using ng generate @angular/material:table .
Update schematics: These schematics are used to update library's dependencies and adjust for breaking changes in a new library release using ng update command. For example, @angular/material update schematic updates material and cdk dependencies using ng update @angular/material command.
The hidden property is used to show or hide the associated DOM element, based on an expression. It can be compared close to ng-show directive in AngularJS. Let's say you want to show user name based on the availability of user using hidden property.
What is the difference between ngIf and hidden property?
The main difference is that *ngIf will remove the element from the DOM, while [hidden] actually plays with the CSS style by setting display:none. Generally it is expensive to add and remove stuff from the DOM for frequent actions.
The index property of the NgFor directive is used to return the zero-based index of the item in each iteration. You can capture the index in a template input variable and use it in the template.
For example, you can capture the index in a variable named indexVar and displays it with the todo's name using ngFor directive as below.
<div*ngFor="let todo of todos; let i=index">{{i +1}}-{{todo.name}}</div>
The main purpose of using *ngFor with trackBy option is performance optimization. Normally if you use NgFor with large data sets, a small change to one item by removing or adding an item, can trigger a cascade of DOM manipulations. In this case, Angular sees only a fresh list of new object references and to replace the old DOM elements with all new DOM elements. You can help Angular to track which items added or removed by providing a trackBy function which takes the index and the current item as arguments and needs to return the unique identifier for this item.
For example, lets set trackBy to the trackByTodos() method
<div*ngFor="let todo of todos; trackBy: trackByTodos">
({{todo.id}}) {{todo.name}}</div>
NgSwitch directive is similar to JavaScript switch statement which displays one element from among several possible elements, based on a switch condition. In this case only the selected element placed into the DOM. It has been used along with NgSwitch, NgSwitchCase and NgSwitchDefault directives.
For example, let's display the browser details based on selected browser using ngSwitch directive.
Is it possible to do aliasing for inputs and outputs?
Yes, it is possible to do aliasing for inputs and outputs in two ways.
Aliasing in metadata: The inputs and outputs in the metadata aliased using a colon-delimited (:) string with the directive property name on the left and the public alias on the right. i.e. It will be in the format of propertyName:alias.
Aliasing with @Input()/@Output() decorator: The alias can be specified for the property name by passing the alias name to the @Input()/@Output() decorator.i.e. It will be in the form of @Input(alias) or @Output(alias).
The safe navigation operator(?)(or known as Elvis Operator) is used to guard against null and undefined values in property paths when you are not aware whether a path exists or not. i.e. It returns value of the object path if it exists, else it returns the null value.
For example, you can access nested properties of a user profile easily without null reference errors as below,
<p>The user firstName is: {{user?.fullName.firstName}}</p>
Using this safe navigation operator, Angular framework stops evaluating the expression when it hits the first null value and renders the view without any errors.
Is any special configuration required for Angular9?
You don't need any special configuration. In Angular9, the Ivy renderer is the default Angular compiler. Even though Ivy is available Angular8 itself, you had to configure it in tsconfig.json file as below,
What are type safe TestBed API changes in Angular9?
Angular 9 provides type safe changes in TestBed API changes by replacing the old get function with the new inject method. Because TestBed.get method is not type-safe. The usage would be as below,
TestBed.get(ChangeDetectorRef)// returns any. It is deprecated now.TestBed.inject(ChangeDetectorRef)// returns ChangeDetectorRef
In Angular 8, the static flag is required for ViewChild. Whereas in Angular9, you no longer need to pass this property. Once you updated to Angular9 using ng update, the migration will remove { static: false } script everywhere.
What is the precedence between pipe and ternary operators?
The pipe operator has a higher precedence than the ternary operator (?:). For example, the expression first ? second : third | fourth is parsed as first ? second : (third | fourth).
An entry component is any component that Angular loads imperatively(i.e, not referencing it in the template) by type. Due to this behavior, they can’t be found by the Angular compiler during compilation. These components created dynamically with ComponentFactoryResolver.
Basically, there are two main kinds of entry components which are following -
A bootstrapped component is an entry component that Angular loads into the DOM during the bootstrap process or application launch time. Generally, this bootstrapped or root component is named as AppComponent in your root module using bootstrap property as below.
@NgModule({declarations: [AppComponent],imports: [BrowserModule,FormsModule,HttpClientModule,AppRoutingModule],providers: [],bootstrap: [AppComponent]// bootstrapped entry component need to be declared here})
You can use ngDoBootstrap hook for a manual bootstrapping of the application instead of using bootstrap array in @NgModule annotation. This hook is part of DoBootstap interface.
The module needs to be implement the above interface to use the hook for bootstrapping.
classAppModuleimplementsDoBootstrap{ngDoBootstrap(appRef: ApplicationRef){appRef.bootstrap(AppComponent);// bootstrapped entry component need to be passed}}
The components referenced in router configuration are called as routed entry components. This routed entry component defined in a route definition as below,
Why is not necessary to use entryComponents array every time?
Most of the time, you don't need to explicity to set entry components in entryComponents array of ngModule decorator. Because angular adds components from both @NgModule.bootstrap and route definitions to entry components automatically.
Do I still need to use entryComponents array in Angular9?
No. In previous angular releases, the entryComponents array of ngModule decorator is used to tell the compiler which components would be created and inserted dynamically in the view. In Angular9, this is not required anymore with Ivy.
Is it all components generated in production build?
No, only the entry components and template components appears in production builds. If a component isn't an entry component and isn't found in a template, the tree shaker will throw it away. Due to this reason, make sure to add only true entry components to reduce the bundle size.
The Angular compiler is used to convert the application code into JavaScript code. It reads the template markup, combines it with the corresponding component class code, and emits component factories which creates JavaScript representation of the component along with elements of @Component metadata.
What is the role of ngModule metadata in compilation process?
The @NgModule metadata is used to tell the Angular compiler what components to be compiled for this module and how to link this module with other modules.
How does angular finds components, directives and pipes?
The Angular compiler finds a component or directive in a template when it can match the selector of that component or directive in that template. Whereas it finds a pipe if the pipe's name appears within the pipe syntax of the template HTML.
Feature modules are NgModules, which are used for the purpose of organizing code. The feature module can be created with Angular CLI using the below command in the root directory,
nggeneratemoduleMyCustomFeature//
Angular CLI creates a folder called my-custom-feature with a file inside called my-custom-feature.module.ts with the following contents
What happens if browserModule used in feature module?
If you do import BrowserModule into a lazy loaded feature module, Angular returns an error telling you to use CommonModule instead. Because BrowserModule’s providers are for the entire app so it should only be in the root module, not in feature module. Whereas Feature modules only need the common directives in CommonModule.
A provider is an instruction to the Dependency Injection system on how to obtain a value for a dependency(aka services created). The service can be provided using Angular CLI as below,
nggenerateservicemy-service
The created service by CLI would be as below,
import{Injectable}from'@angular/core';
@Injectable({providedIn: 'root',//Angular provide the service in root injector})exportclassMyService{}
You should always provide your service in the root injector unless there is a case where you want the service to be available only if you import a particular @NgModule.
It is possible to restrict service provider scope to a specific module instead making available to entire application. There are two possible ways to do it.
There are two possible ways to provide a singleton service.
Set the providedIn property of the @Injectable() to "root". This is the preferred way(starting from Angular 6.0) of creating a singleton service since it makes your services tree-shakable.
What are the different ways to remove duplicate service registration?
If a module defines provides and declarations then loading the module in multiple feature modules will duplicate the registration of the service. Below are the different ways to prevent this duplicate behavior.
Use the providedIn syntax instead of registering the service in the module.
Separate your services into their own module.
Define forRoot() and forChild() methods in the module.
How does forRoot method helpful to avoid duplicate router instances?
If the RouterModule module didn’t have forRoot() static method then each feature module would instantiate a new Router instance, which leads to broken application due to duplicate instances. After using forRoot() method, the root application module imports RouterModule.forRoot(...) and gets a Router, and all feature modules import RouterModule.forChild(...) which does not instantiate another Router.
The Shared Module is the module in which you put commonly used directives, pipes, and components into one module that is shared(import it) throughout the application.
For example, the below shared module imports CommonModule, FormsModule for common directives and components, pipes and directives based on the need,
No, it is not recommended to share services by importing module. i.e Import modules when you want to use directives, pipes, and components only. The best approach to get a hold of shared services is through 'Angular dependency injection' because importing a module will result in a new service instance.
In Angular 9.1, the API method getLocaleDirection can be used to get the current direction in your app. This method is useful to support Right to Left locales for your Internationalization based applications.
import{getLocaleDirection,registerLocaleData}from'@angular/common';import{LOCALE_ID}from'@angular/core';importlocaleArfrom'@angular/common/locales/ar';
...
constructor(@Inject(LOCALE_ID)locale){constdirectionForLocale=getLocaleDirection(locale);// Returns 'rtl' or 'ltr' based on the current localeregisterLocaleData(localeAr,'ar-ae');constdirection=getLocaleDirection('ar-ae');// Returns 'rtl'// Current direction is used to provide conditional logic here}
The ngcc(Angular Compatibility Compiler) is a tool which upgrades node_module compiled with non-ivy ngc into ivy compliant format. The postinstall script from package.json will make sure your node_modules will be compatible with the Ivy renderer.
"scripts": {"postinstall": "ngcc"}
Whereas, Ivy compiler (ngtsc), which compiles Ivy-compatible code.
Angular provides a service called NgZone which creates a zone named angular to automatically trigger change detection when the following conditions are satisfied.
Zone is loaded/required by default in Angular applications and it helps Angular to know when to trigger the change detection. This way, it make sures developers focus on application development rather core part of Angular. You can also use Angular without Zone but the change detection need to be implemented on your own and noop zone need to be configured in bootstrap process. Let's follow the below two steps to remove zone.js,
Remove the zone.js import from polyfills.ts.
/*************************************************************************************************** * Zone JS is required by default for Angular itself. */// import 'zone.js/dist/zone'; // Included with Angular CLI.
By default, Angular CLI creates components in an inline displayed mode(i.e, display:inline). But it is possible to create components with display: block style using displayBlock option,
nggeneratecomponentmy-component--displayBlock
(OR) the option can be turned on by default in Angular.json with schematics.@schematics/angular:component.displayBlock key value as true.
What are the possible data update scenarios for change detection?
The change detection works in the following scenarios where the data changes needs to update the application HTML.
Component initialization: While bootstrapping the Angular application, Angular triggers the ApplicationRef.tick() to call change detection and View Rendering.
Event listener: The DOM event listener can update the data in an Angular component and trigger the change detection too.
Execution Context is an abstract concept that holds information about the environment within the current code being executed. A zone provides an execution context that persists across asynchronous operations is called as zone context. For example, the zone context will be same in both outside and inside setTimeout callback function,
zone.run(()=>{// outside zoneexpect(zoneThis).toBe(zone);setTimeout(function(){// the same outside zone exist hereexpect(zoneThis).toBe(zone);});});
The current zone is retrieved through Zone.current.
There are four lifecycle hooks for asynchronous operations from zone.js.
onScheduleTask: This hook triggers when a new asynchronous task is scheduled. For example, when you call setTimeout()
onScheduleTask: function(delegate,curr,target,task){console.log('new task is scheduled:',task.type,task.source);returndelegate.scheduleTask(target,task);}
onInvokeTask: This hook triggers when an asynchronous task is about to execute. For example, when the callback of setTimeout() is about to execute.
onInvokeTask: function(delegate,curr,target,task,applyThis,applyArgs){console.log('task will be invoked:',task.type,task.source);returndelegate.invokeTask(target,task,applyThis,applyArgs);}
onHasTask: This hook triggers when the status of one kind of task inside a zone changes from stable(no tasks in the zone) to unstable(a new task is scheduled in the zone) or from unstable to stable.
onHasTask: function(delegate,curr,target,hasTaskState){console.log('task state changed in the zone:',hasTaskState);returndelegate.hasTask(target,hasTaskState);}
onInvoke: This hook triggers when a synchronous function is going to execute in the zone.
onInvoke: function(delegate,curr,target,callback,applyThis,applyArgs){console.log('the callback will be invoked:',callback);returndelegate.invoke(target,callback,applyThis,applyArgs);}
What are the methods of NgZone used to control change detection?
NgZone service provides a run() method that allows you to execute a function inside the angular zone. This function is used to execute third party APIs which are not handled by Zone and trigger change detection automatically at the correct time.
exportclassAppComponentimplementsOnInit{constructor(privatengZone: NgZone){}ngOnInit(){// use ngZone.run() to make the asynchronous operation in the angular zonethis.ngZone.run(()=>{someNewAsyncAPI(()=>{// update the data of the component});});}}
Whereas runOutsideAngular() method is used when you don't want to trigger change detection.
exportclassAppComponentimplementsOnInit{constructor(privatengZone: NgZone){}ngOnInit(){// Use this method when you know no data will be updatedthis.ngZone.runOutsideAngular(()=>{setTimeout(()=>{// update component data and don't trigger change detection});});}}
You can change the settings of zone by configuring them in a separate file and import it just after zonejs import. For example, you can disable the requestAnimationFrame() monkey patch to prevent change detection for no data update as one setting and prevent DOM events(a mousemove or scroll event) to trigger change detection. Let's say the new file named zone-flags.js,
The above configuration file can be imported in a polyfill.ts file as below,
/*************************************************************************************************** * Zone JS is required by default for Angular. */import`./zone-flags`;import'zone.js/dist/zone';// Included with Angular CLI.
Angular provides a trigger() function for animation in order to collect the states and transitions with a specific animation name, so that you can attach it to the triggering element in the HTML template. This function watch for changes and trigger initiates the actions when a change occurs. For example, let's create trigger named upDown, and attach it to the button element.
How do you configure injectors with providers at different levels?
You can configure injectors with providers at different levels of your application by setting a metadata value. The configuration can happen in one of three places,
In the @Injectable() decorator for the service itself
Is it mandatory to use injectable on every service class?
No. The @Injectable() decorator is not strictly required if the class has other Angular decorators on it or does not have any dependencies. But the important thing here is any class that is going to be injected with Angular is decorated. i.e, If we add the decorator, the metadata design:paramtypes is added, and the dependency injection can do it's job. That is the exact reason to add the @Injectable() decorator on a service if this service has some dependencies itself. For example, Let's see the different variations of AppService in a root component,
The below AppService can be injected in AppComponent without any problems. This is because there are no dependency services inside AppService.
exportclassAppService{constructor(){console.log('A new app service');}}
The below AppService with dummy decorator and httpService can be injected in AppComponent without any problems. This is because meta information is generated with dummy decorator.
and the generated javascript code of above service has meta information about HttpService, js var AppService = (function () { function AppService(http) { console.log(http); } AppService = __decorate([ core_1.Injectable(), __metadata('design:paramtypes', [http_service_1.HttpService]) ], AppService); return AppService; }()); exports.AppService = AppService; 3. The below AppService with @injectable decorator and httpService can be injected in AppComponent without any problems. This is because meta information is generated with Injectable decorator. js @Injectable({ providedIn: 'root', }) export class AppService { constructor(http: HttpService) { console.log(http); } } ⬆
What is an optional dependency?
The optional dependency is a parameter decorator to be used on constructor parameters, which marks the parameter as being an optional dependency. Due to this, the DI framework provides null if the dependency is not found. For example, If you don't register a logger provider anywhere, the injector sets the value of logger(or logger service) to null in the below class.
import{Optional}from'@angular/core';constructor(@Optional()privatelogger?: Logger){if(this.logger){this.logger.log('This is an optional dependency message');}else{console.log('The logger is not registered');}}
There are two types of injector hierarchies in Angular
ModuleInjector hierarchy: It configure on a module level using an @NgModule() or @Injectable() annotation.
ElementInjector hierarchy: It created implicitly at each DOM element. Also it is empty by default unless you configure it in the providers property on @Directive() or @Component().
Reactive forms is a model-driven approach for creating forms in a reactive style(form inputs changes over time). These are built around observable streams, where form inputs and values are provided as streams of input values. Let's follow the below steps to create reactive forms,
Register the reactive forms module which declares reactive-form directives in your app
import{ReactiveFormsModule}from'@angular/forms';
@NgModule({imports: [// other imports ...ReactiveFormsModule],})exportclassAppModule{}
Create a new FormControl instance and save it in the component.
Dynamic forms is a pattern in which we build a form dynamically based on metadata that describes a business object model. You can create them based on reactive form API. ⬆
What are template driven forms?
Template driven forms are model-driven forms where you write the logic, validations, controls etc, in the template part of the code using directives. They are suitable for simple scenarios and uses two-way binding with [(ngModel)] syntax. For example, you can create register form easily by following the below simple steps,
Import the FormsModule into the Application module's imports array
Attach NgForm directive to the tag in order to create FormControl instances and register them
<form #registerForm="ngForm">
Apply the validation message for form controls
<labelfor="name">Name</label><inputtype="text" class="form-control" id="name"
required[(ngModel)]="model.name" name="name"
#name="ngModel"><div[hidden]="name.valid || name.pristine"
class="alert alert-danger">
Please enter your name
</div>
Let's submit the form with ngSubmit directive and add type="submit" button at the bottom of the form to trigger form submit.
<form(ngSubmit)="onSubmit()" #heroForm="ngForm">
// Form goes here
<buttontype="submit" class="btn btn-success" [disabled]="!registerForm.form.valid">Submit</button>
Finally, the completed template-driven registration form will be appeared as follow.
<divclass="container"><h1>Registration Form</h1><form(ngSubmit)="onSubmit()" #registerForm="ngForm"><divclass="form-group"><labelfor="name">Name</label><inputtype="text" class="form-control" id="name"
required[(ngModel)]="model.name" name="name"
#name="ngModel"><div[hidden]="name.valid || name.pristine"
class="alert alert-danger">
Please enter your name
</div></div><buttontype="submit" class="btn btn-success" [disabled]="!registerForm.form.valid">Submit</button></form></div>
What are the different ways to group form controls?
Reactive forms provide two ways of grouping multiple related controls.
FormGroup: It defines a form with a fixed set of controls those can be managed together in an one object. It has same properties and methods similar to a FormControl instance. This FormGroup can be nested to create complex forms as below.
import{Component}from'@angular/core';import{FormGroup,FormControl}from'@angular/forms';
@Component({selector: 'user-profile',templateUrl: './user-profile.component.html',styleUrls: ['./user-profile.component.css']})exportclassUserProfileComponent{userProfile=newFormGroup({firstName: newFormControl(''),lastName: newFormControl(''),address: newFormGroup({street: newFormControl(''),city: newFormControl(''),state: newFormControl(''),zip: newFormControl('')})});onSubmit(){// Store this.userProfile.value in DB}}
<form[formGroup]="userProfile" (ngSubmit)="onSubmit()"><label>
First Name:
<inputtype="text" formControlName="firstName"></label><label>
Last Name:
<inputtype="text" formControlName="lastName"></label><divformGroupName="address"><h3>Address</h3><label>
Street:
<inputtype="text" formControlName="street"></label><label>
City:
<inputtype="text" formControlName="city"></label><label>
State:
<inputtype="text" formControlName="state"></label><label>
Zip Code:
<inputtype="text" formControlName="zip"></label></div><buttontype="submit" [disabled]="!userProfile.valid">Submit</button></form>
FormArray: It defines a dynamic form in an array format, where you can add and remove controls at run time. This is useful for dynamic forms when you don’t know how many controls will be present within the group.
import{Component}from'@angular/core';import{FormArray,FormControl}from'@angular/forms';
@Component({selector: 'order-form',templateUrl: './order-form.component.html',styleUrls: ['./order-form.component.css']})exportclassOrderFormComponent{constructor(){this.orderForm=newFormGroup({firstName: newFormControl('John',Validators.minLength(3)),lastName: newFormControl('Rodson'),items: newFormArray([newFormControl(null)])});}onSubmitForm(){// Save the items this.orderForm.value in DB}onAddItem(){this.orderForm.controls.items.push(newFormControl(null));}onRemoveItem(index){this.orderForm.controls['items'].removeAt(index);}}
<form[formControlName]="orderForm" (ngSubmit)="onSubmit()"><label>
First Name:
<inputtype="text" formControlName="firstName"></label><label>
Last Name:
<inputtype="text" formControlName="lastName"></label><div><p>Add items</p><ulformArrayName="items"><li*ngFor="let item of orderForm.controls.items.controls; let i = index"><inputtype="text" formControlName="{{i}}"><buttontype="button" title="Remove Item" (click)="onRemoveItem(i)">Remove</button></li></ul><buttontype="button" (click)="onAddItem">
Add an item
</button></div>
How do you update specific properties of a form model?
You can use patchValue() method to update specific properties defined in the form model. For example,you can update the name and street of certain profile on click of the update button as shown below.
FormBuilder is used as syntactic sugar for easily creating instances of a FormControl, FormGroup, or FormArray. This is helpful to reduce the amount of boilerplate needed to build complex reactive forms. It is available as an injectable helper class of the @angular/forms package.
For example, the user profile component creation becomes easier as shown here.
You can add a getter property(let's say, diagnostic) inside component to return a JSON representation of the model during the development. This is useful to verify whether the values are really flowing from the input box to the model and vice versa or not.
exportclassUserProfileComponent{model=newUser('John',29,'Writer');// TODO: Remove after the verificationgetdiagnostic(){returnJSON.stringify(this.model);}}
and add diagnostic binding near the top of the form
{{diagnostic}}
<divclass="form-group">
// FormControls goes here
</div>
What are the state CSS classes provided by ngModel?
The ngModel directive updates the form control with special Angular CSS classes to reflect it's state. Let's find the list of classes in a tabular format,
In a model-driven form, you can reset the form just by calling the function reset() on our form model. For example, you can reset the form model on submission as follows,
onSubmit(){if(this.myform.valid){console.log("Form is submitted");// Perform business logic herethis.myform.reset();}}
Now, your form model resets the form back to its original pristine state.
In reactive forms, the validators can be either synchronous or asynchronous functions,
Sync validators: These are the synchronous functions which take a control instance and immediately return either a set of validation errors or null. Also, these functions passed as second argument while instantiating the form control. The main use cases are simple checks like whether a field is empty, whether it exceeds a maximum length etc.
Async validators: These are the asynchronous functions which take a control instance and return a Promise or Observable that later emits a set of validation errors or null. Also, these functions passed as second argument while instantiating the form control. The main use cases are complex validations like hitting a server to check the availability of a username or email.
The representation of these validators looks like below
In reactive forms, you can use built-in validator like required and minlength on your input form controls. For example, the registration form can have these validators on name input field
How do you optimize the performance of async validators?
Since all validators run after every form value change, it creates a major impact on performance with async validators by hitting the external API on each keystroke. This situation can be avoided by delaying the form validity by changing the updateOn property from change (default) to submit or blur. The usage would be different based on form types,
Template-driven forms: Set the property on ngModelOptions directive
Sometimes you may need to both ngFor and ngIf on the same element but unfortunately you are going to encounter below template error.
Template parse errors: Can't have multiple template bindings on one element.
In this case, You need to use either ng-container or ng-template. Let's say if you try to loop over the items only when the items are available, the below code throws an error in the browser
<ul*ngIf="items" *ngFor="let item of items"><li></li></ul>
and it can be fixed by
<ng-container*ngIf="items"><ul*ngFor="let item of items"><li></li></ul></ng-container>
The :host pseudo-class selector is used to target styles in the element that hosts the component. Since the host element is in a parent component's template, you can't reach the host element from inside the component by other means. For example, you can create a border for parent element as below,
A component harness is a testing API around an Angular directive or component to make tests simpler by hiding implementation details from test suites. This can be shared between unit tests, integration tests, and end-to-end tests. The idea for component harnesses comes from the PageObject pattern commonly used for integration testing.
What is the benefit of Automatic Inlining of Fonts?
During compile time, Angular CLI will download and inline the fonts that your application is using. This performance update speed up the first contentful paint(FCP) and this feature is enabled by default in apps built with version 11.
Hydration is the process that restores the server side rendered application on the client. This includes things like reusing the server rendered DOM structures, persisting the application state, transferring application data that was retrieved already by the server, and other processes.
To enable hydration, we have to enable server side rendering or Angular Universal. Once enabled, we can add the following piece of code in the root component.
.jpeg)
.jpeg)
