With reactive forms, you will discover that it is easier to build cleaner forms. Because every JavaScript framework advises that you don’t make the template clustered, this has become a priority as the form logic now lies in the component class.
It also reduces the need to use a lot of directives and even end-to-end testing since you can now easily test your forms. It gives the developer all the control, and nothing is implicit anymore — every choice about inputs and controls must be made intentionally and, of course, explicitly.
In Angular, form controls are classes that can hold both the data values and the validation information of any form element. That is to say, every form input you have in a reactive form should be bound by a form control.
These are the basic units that make up reactive forms. In this article, you will be shown how form controls can be divided by form groups to create clusters to provide a platform to easily access the template element as groups.
Form groups wrap a collection of form controls; just as the control gives you access to the state of an element, the group gives the same access but to the state of the wrapped controls. Every single form control in the form group is identified by name when initializing.
A FormGroup
aggregates the values of each child FormControl
into one object, with each control name as the key. It calculates its status by reducing the status values of its children.
To be able to follow through this article’s demonstration, you should have:
// run the command in a terminal ng version
Confirm that you are using version 8, and update to 8 if you are not.
npm install
Other things that would be nice to have are:
To illustrate the concept of form groups, we will go through the process of building a reactive form so that you can fully grasp how to set it up with form groups. From here, we assume you have downloaded the starter project on GitHub and opened it in VS Code.
The first thing to do is to tell Angular that you want to make use of the form group by importing it inside the appropriate component. Navigate to the employee.component.ts
file and copy in the code block below:
import { Component, OnInit } from '@angular/core'; import { FormControl, FormGroup } from '@angular/forms' @Component({ selector: 'app-employee', templateUrl: './employee.component.html', styleUrls: ['./employee.component.css'] }) export class EmployeeComponent implements OnInit { bioSection = new FormGroup({ firstName: new FormControl(''), lastName: new FormControl(''), age: new FormControl('') }); constructor() { } ngOnInit() { } }
Here the form group was both imported and initialized to group together some form controls that compose the bio section of the form. To reflect this group, you have to associate the model to the view with the form group name, like this:
// copy inside the employee.component.html file <form [formGroup]="bioSection" (ngSubmit)="callingFunction()"><label>
First Name:
<input type=“text” formControlName=“firstName”>
</label>
<label>
Last Name:
<input type=“text” formControlName=“lastName”>
</label>
<label>
Age:
<input type=“text” formControlName=“age”>
</label>
<button type=“submit”>Submit Application</button>
</form>
Just like the form control, the form group name is used to identify the form group in the view, and on submit, the callingFunction
will be triggered. Your app.component.html
file should look like this:
<div style=“text-align:center”>
<h2>Angular Job Board </h2>
<app-employee></app-employee>
</div>
Now run your application in development with the command:
ng serve
It should look like this:
Yes, the reactive forms API makes it possible to nest a form group inside another form group. Copy the code block below into the employee.component.ts
file:
import { Component, OnInit } from ‘@angular/core’;
import { FormControl, FormGroup } from ‘@angular/forms’
@Component({
selector: ‘app-employee’,
templateUrl: ‘./employee.component.html’,
styleUrls: [‘./employee.component.css’]
})
export class EmployeeComponent implements OnInit {
bioSection = new FormGroup({
firstName: new FormControl(‘’),
lastName: new FormControl(‘’),
age: new FormControl(‘’),
stackDetails: new FormGroup({
stack: new FormControl(‘’),
experience: new FormControl(‘’)
}),
address: new FormGroup({
country: new FormControl(‘’),
city: new FormControl(‘’)
})
});
constructor() { }
ngOnInit() {
}
callingFunction() {
console.log(this.bioSection.value);
}
}
Here you see that the main form group wrapper is the bio section inside which both the stack details group and the address group is nested. It is important to note — as you see in the code block — that nested form groups are not defined by the assignment statement, but rather with the colon, just like you will a form control. Reflecting this in the view will look like this:
// copy inside the employee.component.html file
<form [formGroup]=“bioSection” (ngSubmit)=“callingFunction()”>
<h3>Bio Details
</h3><label>
First Name:
<input type=“text” formControlName=“firstName”>
</label> <br>
<label>
Last Name:
<input type=“text” formControlName=“lastName”>
</label> <br>
<label>
Age:
<input type=“text” formControlName=“age”>
</label>
<div formGroupName=“stackDetails”>
<h3>Stack Details</h3><label> Stack: <input type="text" formControlName="stack"> </label> <br> <label> Experience: <input type="text" formControlName="experience"> </label>
</div>
<div formGroupName=“address”>
<h3>Address</h3><label> Country: <input type="text" formControlName="country"> </label> <br> <label> City: <input type="text" formControlName="city"> </label>
</div>
<button type=“submit”>Submit Application</button>
</form>
It is very important that every name in the model and the view match — you do not misspell the form control names! When you save and run the application, if you do get any errors, read the error message and correct the misspelling you must have used. You can style your component with the style instructions below:
input[type=text] {
width: 30%;
padding: 8px 14px;
margin: 2px;
box-sizing: border-box;
}
button {
font-size: 12px;
margin: 2px;
padding: 8px 14px;
}
If you run the application, you should see something like this in your browser:
When you use the form and submit, you will see your input results returned in the browser console. The complete code to this tutorial can be found here on GitHub.
In addition to learning about form controls, you have now been introduced to the important concept of grouping these controls. You were also shown why grouping them is very important, as it ensures that their collective instances can be captured at once. The next concept we will be looking at is form builders.
Thanks for reading. If you liked this post, share it with all of your programming buddies!
Further reading
☞ Best 50 Angular Interview Questions for Frontend Developers in 2019
☞ To become an Outstanding AngularJs Developer - part 2
☞ To become an Outstanding AngularJs Developer - part 1
☞ To become an effective Angular developer, you need to learn 19 things in this article
☞ Top 18 Mistakes AngularJS Developers Makes
☞ AngularJS Directive with Example: ng-init, ng-app, ng-repeat, ng-model
☞ Angular 8 (formerly Angular 2) - The Complete Guide
Originally published on blog.logrocket.com
#angular #angular-js #javascript #web-development