Skip to main content

Angular(Version 10) Date Picker Range Selection In Angular Material UI


In Angular Material Version 10, announced a new feature in date selection is Date Picker Range Selection. Before Angular V10 for date range selection need to write custom code or need to use third-party plugins. So now by upgrading to Angular V10, we can grab this new feature of a Date Range selection.

Default Core Components Of Date Range Selection:

The default core component of date range selection of Date Picker in Angular Material is:
  • mat-date-range-picker
  • mat-date-range-input
mat-date-range-picker is an Angular Material Component for date range selection. mat-date-range-picker component is shown popup calendar like mat-datepicker component but allows multi-date selection option.

mat-date-range-input is an Angular Material Component for the date range selection. This component requires to input fields to capture the start date and end date that are selected from mat-date-rang-picker.

Create Sample Angular(V10) Application:

Let's create a sample application to implement the date range selection date picker. Not to forgot this sample example only works with Angular v10.
Skip this section if you know how to create angular application and configure angular material
Commands:
Run this command to install Angular CLI command on your system:

npm install -g @angular/cli
Run this Angular CLI command to generate angular application:

ng new your-project-name
Run the following command to add Angular Material:

ng add @angular/material
Run the following command to start angular application:

ng serve

Add Date Range Selection Material Component:

Now to add material date picker with date range selection to it, then we need to add material components as below.
src/app/app.component.html:
<mat-form-field >
  <mat-label>Enter a date range</mat-label>
  <mat-date-range-input  [rangePicker]="myPicker">
    <input matStartDate placeholder="Start date">
    <input matEndDate placeholder="End date">
  </mat-date-range-input>
  <mat-datepicker-toggle matSuffix [for]="myPicker"></mat-datepicker-toggle>
  <mat-date-range-picker #myPicker></mat-date-range-picker>
</mat-form-field>
  • #L1 at this line mat-form-field is an angular material component for form fields
  • #L2 at this line mat-label is an angular material component to represent HTML labels
  • #L3-#L6 at these lines mat-date-range-input is an angular material component for date range selection. This component renders with 2 input fields inside of it. These 2 input fields used to capture date range selection values like start and end dates. These 2 input fields decorated with directives like matStartDate and matEndDate to respond for date picker selection. mat-date-range-input component makes communication with mat-date-range-picker component by using [rangePicker] directive, to this [rangePicker] directive we need to assign template variable(in our example myPicker is template variable of mat-date-range-picker).
  • #L7 at this line mat-datepicker-toggle is an angular material component represents calendar icon inside the input field and on clicking this icon calendar will toggle. To appear this icon to the rightmost side of the input filed needs to use the matSuffix directive. mat-datepicker-toggle also configure with [for] directive which has the value of template variable(in our example myPicker is template variable of mat-date-range-picker).
  • #L8 at this line mat-date-range-picker is an angular material component that shows a calendar popup with a date range selection feature.

Import Material Modules:

Now before the test, our date picker needs to load a few angular material modules like below.
  • MatFormFieldModule
  • MatDatePickerModule
  • MatNativeDateModule
src/app/app.module.ts:
import { MatDatepickerModule } from '@angular/material/datepicker';
import { MatFormFieldModule } from '@angular/material/form-field';
import { MatNativeDateModule } from '@angular/material/core';
// code hidden for display pupose
@NgModule({
  imports: [
    MatDatepickerModule,
    MatFormFieldModule,
    MatNativeDateModule
  ],
})
export class AppModule {}
Now, let's run the application and output shows as below.

Reactive Form Implementation For Date Range Selection:

Let's write a sample example to use this date range selection date picker in angular reactive forms implementation.

The first step to import ReactiveFormsModule from the '@angular/forms' package.
src/app/app.module.ts:
import { ReactiveFormsModule } from '@angular/forms';

@NgModule({
  imports: [
    ReactiveFormsModule
  ]
})
export class AppModule {}
// code hidden for display purpose
Now to create FormGroup or FormControl instances it easy to do by importing FormBuilder instance.
src/app/app.component.ts:
import { Component, OnInit } from '@angular/core';
import { FormBuilder, FormGroup } from '@angular/forms';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css'],
})
export class AppComponent implements OnInit {
  dateSelectorGroup:FormGroup;
  displayStartDate:string = "N/A";
  displayEndDate:string = "N/A";
 
  constructor(private fb:FormBuilder) {
    
  }
  ngOnInit(): void {
    this.initializeForm();
  }

  initializeForm(){
    this.dateSelectorGroup = this.fb.group({
      startDate:[''],
      endDate:['']
    });

    this.dateSelectorGroup.controls.startDate.valueChanges.subscribe(value => {
      if(value){
        this.displayStartDate = value;
      }
      else{
        this.displayStartDate = "N/A"
      }
    });

    this.dateSelectorGroup.controls.endDate.valueChanges.subscribe(value => {
      if(value){
        this.displayEndDate = value;
      }
      else{
        this.displayEndDate = "N/A"
      }
    })
  }
}
  • #L2 at this line FormBuilder, FormGroup instances are importing from '@angular/forms' package
  • #L10 at this line initialized a variable 'dateSelectorGroup' of type FormGroup, this FormGroup variable is used in the Html component to establish a reactive form communication.
  • #L11-L12 at these lines declared variables like 'displayStartDate', 'displayEndDate'. The idea behind to declare these variables to assign the date picker selected values to display.
  • #L14 at this line FormBuilder injected into the component constructor.
  • #L21-L44 at these lines method like 'initializeform()' setup to add reactive form and register the form control change events.
  • #L22-25 at these lines FormGroup instance created from FormBuilder and assigned to 'dateSelectorGroup' variable.
  • #L27-34  at these lines capturing the value change event of 'startDate' form control and assigning the changed value to 'displayStartDate' variable.
  • #L36-43  at these lines capturing the value change event of 'endDate' form control and assigning the changed value to 'displayEndDate' variable.
src/app/app.component.html:
<mat-form-field >
  <mat-label>Enter a date range</mat-label>
  <mat-date-range-input [formGroup]="dateSelectorGroup"  [rangePicker]="myPicker">
    <input matStartDate formControlName="startDate" placeholder="Start date">
    <input matEndDate formControlName="endDate" placeholder="End date">
  </mat-date-range-input>
  <mat-datepicker-toggle matSuffix [for]="myPicker"></mat-datepicker-toggle>
  <mat-date-range-picker #myPicker></mat-date-range-picker>
</mat-form-field>
<div>
  <div>
    <span>State Date:</span> <span>{{displayStartDate}}</span>
  </div>
  <div>
    <span>End Date:</span> <span>{{displayEndDate}}</span>
  </div>
</div>
  • #L3 at this line FromGroupDirective was declared by assigning the 'dateSelectorGroup' variable
  • #L4-L5 at these lines FormControlDirectives was declared on input fields
  • #L10-L17 at these line angular interpolation binding was performed to display selected dates.
Now run the application then select the start and end dates and output shows as below.

Wrapping Up:

Hopefully, I think this article delivered some useful information on the Date Picker Range Selection In Angular Material(V10). I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:

Comments

Popular posts from this blog

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

.Net5 Web API Managing Files Using Azure Blob Storage

In this article, we are going to understand the different file operations like uploading, reading, downloading, and deleting in .Net5 Web API application using Azure Blob Storage. Azure Blob Storage: Azure blob storage is Microsoft cloud storage. Blob storage can store a massive amount of file data as unstructured data. The unstructured data means not belong to any specific type, which means text or binary data. So something like images or pdf or videos to store in the cloud, then the most recommended is to use the blob store. The key component to creating azure blob storage resource: Storage Account:- A Storage account gives a unique namespace in Azure for all the data we will save. Every object that we store in Azure Storage has an address. The address is nothing but the unique name of our Storage Account name. The combination of the account name and the Azure Storage blob endpoint forms the base address for each object in our Storage account. For example, if our Storage Account is n

.Net5 Web API Redis Cache Using StackExchange.Redis.Extensions.AspNetCore Library

In this article, we are going to explore the integration of Redis cache in .Net5 Web API application using the 'StackExchange.Redis.Exntensions' library. Note:- Microsoft has introduced an 'IDistributedCache' interface in dotnet core which supports different cache stores like In-Memory, Redis, NCache, etc. It is simple and easy to work with  'IDistributedCache', for the Redis store with limited features but if we want more features of the Redis store we can choose to use 'StackExchange.Redis.Extensions'.  Click here for Redis Cache Integration Using IDistributedCache Interface . Overview On StackExchange.Redis.Extnesions Library: The 'StackExchange.Redis.Extension' library extended from the main library 'StackExchange.Redis'. Some of the key features of this library like: Default serialization and deserialization. Easy to save and fetch complex objects. Search key. Multiple Database Access Setup Redis Docker Instance: For this sampl

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route. An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaul

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library  jQuery Validate . In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples. Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio. Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as bel

NestJS File Upload

In this article, we are going to understand the steps to create a file uploading endpoint in the NestJS application. Key Features In NestJS File Upload: Let us know some key features of NestJS file upload before implementing a sample application. FileInterceptor: The 'FileInterceptor' will be decorated on top of the file upload endpoint. This interceptor will read single file data from the form posted to the endpoint. export declare function FilesInterceptor(fieldName: string, localOptions?: MulterOptions): Type<NestInterceptor>; Here we can observe the 'fieldName' first input parameter this value should be a match with our 'name' attribute value on the form file input field. So our interceptor read our files that are attached to the file input field. Another input parameter of 'MulterOptions' that provides configuration like file destination path, customizing file name, etc. FilesInterceptor: The 'FilesInterceptor' will be decorated on t

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload: The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client.  Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file.  Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk.  If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application. Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.   Check the link to use the Visual Studio Code for .NET Core Application . IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files f

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items. The main building block of ion-picker as follows: PickerController PickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker. Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger&quo

.Net Core HttpClient JSON Extension Methods Using System.Net.Http.Json Package

.Net Core 3.0 onwards Microsoft brought up a new package called System.Net.Http.Json. This new package provides JSON extension methods for HttpClient. These JSON extension methods will have a prebuild mechanism for serializing or deserializing response data or payload of HttpClient call. System.Net.Http.Json extension methods that are provided to HttpClient, few of them are mentioned below. GetFromJsonAsync PostAsJsonAsync PutAsJsonAsync ReadFromJsonAsync In this article, we understand System.Net.Http.Json package by implementing the HttpClient samples by with and without JSON extension methods and compare them. Create A .Net Core Web API Sample Application: Let's create a .Net Core sample Web API application, from this application we will consume another Web API by implementing HttpClient calls. We can create a Web API sample application using IDE like Visual Studio 2019(Supports .Net Core 3.0 plus) or  Visual Studio Code . Create A Typed Client: In .Net Core using the Http