Skip to main content

A Demo On Angular(v12) Pagination Using Angular Material UI Paginator Component

In this article, we are going to implement pagination using angular material in a sample angular(version 12) application.

Create A Sample Angular Application:

Let's create a sample angular project and also install the angular material package.

Install Angular CLI:
npm install -g @angular/cli

Command To Create Angular Application:
ng new your-project-name

Command To Install Angular Material Package:
ng add @angular/material


Here I'm going to use a sample pagination API that I had created. Here I will show the sample response to gain the basic idea over the API.

Create Response Models:

Now let's create models to read the API JSON response.
ng g class models/todo.model

ng g class models/todo.paging.model

export interface TodoModel {
	itemName: string;
import { TodoModel } from "./todo.model";

export interface TodoPagingModel {
    data: TodoModel[],

Create A Service Class To Invoke API Endpoint:

Now let's create an angular service class to consume the API endpoint.
ng g service app

import { Injectable } from '@angular/core';
import { HttpClient } from '@angular/common/http';
import { TodoPagingModel } from './models/todo.paging.model';
import { Observable } from 'rxjs';

  providedIn: 'root',
export class AppService {
  constructor(private httpClient: HttpClient) {}

  getTodos(currentPage: number, pageSize: number): Observable<TodoPagingModel> {
    return this.httpClient.get<TodoPagingModel>(
  • Here using the 'HttpClient' instance invoking the GET call using 'currentPage' and 'pageSize' as query parameters.
Import the 'HttpClientModule' and 'AppService' into the 'app.module.ts'
import { AppService } from './app.service';
import { HttpClientModule } from '@angular/common/http';
// code hidden for display purpose
  imports: [
  providers: [AppService]
export class AppModule {}

Implement Pagination:

Now let's update our 'AppComponent' with our pagination logic.
    <table mat-table [dataSource]="todos">
      <ng-container matColumnDef="id">
        <th mat-header-cell *matHeaderCellDef>Id</th>
        <td mat-cell *matCellDef="let row">{{ }}</td>
      <ng-container matColumnDef="itemName">
        <th mat-header-cell *matHeaderCellDef>Item Name</th>
        <td mat-cell *matCellDef="let row">{{ row.itemName }}</td>
      <ng-container matColumnDef="isCompleted">
        <th mat-header-cell *matHeaderCellDef>Is Completed</th>
        <td mat-cell *matCellDef="let row">{{ row.isCompleted }}</td>

      <tr mat-header-row *matHeaderRowDef="columnsToDisplay"></tr>
      <tr mat-row *matRowDef="let row; columns: columnsToDisplay"></tr>
    [pageSizeOptions]="[5, 10, 15]"
  • (Line: 3) The 'dataSource' property needs to assign our data collection that has to be bind to the table.
  • Here registered each column of the table with respective columns and cells with the respective data binding property. Each column will be registered uniquely with the help of 'matColumnDef', so its value should be unique.
  • (Line: 17) Assigning the variable 'columnsToDisplay' of type array that contains a collection of column names(these names should match with the 'matColumnDef' values). Only columns that are available in the array will be displayed, in spite of we register more columns in the HTML.
  • (Line: 21-26) Rendered the 'mat-paginator' component. The directive 'showFirstLastButons' displays the first and last pagination buttons on UI. The 'pageSizeOptions' define the values of the different page sizes that are available in the drop-down selection. The 'length' value is our total number of records at the server. The 'pageSize' value represents the initial page size of the table.
import { Component, ViewChild, AfterViewInit } from '@angular/core';
import { MatPaginator } from '@angular/material/paginator';
import { switchMap, map } from 'rxjs/operators';
import { AppService } from './app.service';
import { TodoModel } from './models/todo.model';

  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
export class AppComponent implements AfterViewInit {
  title = 'ang12-paging';
  columnsToDisplay = ['id', 'itemName', 'isCompleted'];
  totalRecords = 0;
  todos:TodoModel[] = [];

  @ViewChild(MatPaginator) paginator?:MatPaginator;

  constructor(private appService:AppService){}

  ngAfterViewInit(): void {

    let currentPage = (this.paginator?.pageIndex ?? 0)+1;
    this.appService.getTodos(currentPage,  (this.paginator?.pageSize ?? 0))
    .subscribe(result => {
      this.totalRecords = result.totalCount;
      this.todos =;

      switchMap(() => {
        let currentPage = (this.paginator?.pageIndex ?? 0)+1;
        return this.appService.getTodos(currentPage, (this.paginator?.pageSize ?? 0));
      map( result => {
          return [];
        this.totalRecords = result.totalCount;
    .subscribe(data => {
      this.todos = data;
  • (Line: 15) The 'columnsToDisplay' array contains the columns that need to be shown, so with this variable, we can dynamically display our table columns if we need.
  • (Line: 16) The 'totalRecords' variable holds the records count at the server, whose value is fetched from the API call.
  • (Line: 17) The 'todos' variable of type is a collection of our  'TodoModel'. So the data inside of this variable will be bind to HTML.
  • (Line: 19) The 'MatPaginator' holds the reference to the component through with we can listen to the page changes in our component.
  • (Line: 23-26) Here we implemented one of the life cycle methods like 'ngAfterViewInit'. Since we mainly depend on 'MatPaginator' child component whose memory will be allocated after HMTL rendering, that is the reason behind using the 'ngAfterViewInit'.
  • (Line: 25-35) On angular page loads to make an initial API request this method will be helpful. So for API requests, we need query params like 'currentPage' and 'pageSize' those values available from the 'MatPaginator'. The 'MatPaginator' page index starts from '0', so we need to increment it by '1' and then pass it to the API call.
  • (Line: 37-54) Here we register the page change event, so this will get executed on every event raised from the pagination component. The page event will be passed to the 'pipe', then using 'switchMap'(rxjs operator) we returning the new observable that is our API call, which means we are switching from page change event to API call event. After a successful API request, data will be assigned to respective variables.
We have used angular material 'Table' and 'Pagination' components, so we have to import them into 'AppModule'.
import { MatTableModule } from '@angular/material/table';
import { MatPaginatorModule } from '@angular/material/paginator';

// code hidden for display purpose

  imports: [
export class AppModule {}
Now let's run our application and check the output.

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information on Angular pagination using the Angular Material component. I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:


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

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

.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

.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

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 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