Skip to main content

Pagination In Vue3 Application Using '@ocrv/vue-tailwind-pagination' Plugin

In this article, we will understand the pagination in the Vue3 application using the '@ocrv/vue-tailwind-pagination' plugin.

Key Features Of Plugin:

  • current - The 'current' property to set the current page number.
  • total - The 'total' property that represents the number of records for the table content. So based on this 'total' property value, the total number of page numbers display depends.
  • per-page - The 'per-page' property to set the count for the records to display for each page.
  • page-changed - The 'page-changed' event that raises on selecting the page. It outputs  '$event' which is nothing but the selected page number.

Create A Vue3 Sample Application:

To implement our pagination sample let's begin by creating a Vue3 sample application.
Command To Create Vue3 Application:
Vue Create Your_Sample_App_name

Install Tailwind Pagination NPM Package:

Tailwind Pagination NPM Package Command:
npm install --save @ocrv/vue-tailwind-pagination

Configure And Implement Pagination Component:

Let's visualize the pagination component by integrating it. So here I'm going to use the existing 'HelloWorld.vue' component to render the pagination component, so clear up the existing code and add the following.
src/components/HelloWorld.vue:(Html Part)
<template>
  <div class="hello">
    <VueTailwindPagination
      :current="currentPage"
      :total="total"
      :per-page="perPage"
      @page-changed="onPageClick($event)"
    />
  </div>
</template>
  • (Line 3) Rendering the 'VueTailwindPagination' vue component.
  • Pagination component configured with key features like 'current', 'total', 'per-page' input properties. Also registered a 'page-changed' event which fires on clicking the page. The '$event' outputs by the 'page-changed' event are clicked page numbers.
<script>
import "@ocrv/vue-tailwind-pagination/dist/style.css";
import VueTailwindPagination from "@ocrv/vue-tailwind-pagination";
export default {
  components: {
    VueTailwindPagination,
  },
  data() {
    return {
      currentPage: 1,
      perPage: 2,
      total: 100,
    };
  },
  methods:{
    onPageClick(event){
      this.currentPage = event;
    }
  }
};
</script>
  • (Line: 2) Importing our pagination component CSS file which contains tailwind CSS styles.
  • (Line: 3) Importing the 'VueTailwindPagination' vue component from the '@ocr/vue-tailwind-paginatin' library.
  • (Line: 6) Register 'VueTailwindPagination' component.
  • (Line: 10) The 'currentPage' variable represents the selected page number. The 'currentPage' value will be assigned to 'current' property of the pagination vue component.
  • (Line: 11) The 'perPage' variable represents the records to display for a page in a table. So using this 'perPage' value and the total number of records our pagination components calculates the number of page numbers to be generated. The value of 'perPage' will be assigned to 'per-page' property of the pagination vue component
  • (Line: 12) The 'total' variable represents the total records for the table content.
  • (Line: 16-18) The 'onPageClick' is callback method for the event 'page-changed'. This method invoked on selecting a page and then assigning the selected page value to the variable 'currentPage'.

Third-Party Rest API:

We will upgrade our sample to work with real-time API which filters data based on page numbers. Here I'm using free rest API for our sample like "https://reqres.in/api/users?page=1". The JSON response from the API looks as below.
Here from the image response contains properties like:
  • 'page' - current selected page.
  • 'per-page' - number of records count per page.
  • 'total' - total record count.

Install Axios Plugin:

In vue to invoke API's best plugin to use is 'Axios'.
Axios Command:
npm install axios

Invoke API And Render The Response To A Table:

Now we will update our sample to consume API and test our pagination to invoke the API per page click.

I will use the bootstrap table to display the response content and the content will be changed on page click. So first let's add the bootstrap CSS file in the index.html.
public/index.html:
<link 
href="https://cdn.jsdelivr.net/npm/bootstrap@5.0.0-beta2/dist/css/bootstrap.min.css" 
rel="stylesheet" 
integrity="sha384-BmbxuPwQa2lc/FVzBcNJ7UAyJxM6wuqIj61tLrc4wSX0szH/Ev+nYRRuWlolflfl" crossorigin="anonymous">
Let's update our sample now in 'Helloworld.vue' file.
src/components/Helloworld.vue:(Html Part)
<template>
  <div class="hello">
    <VueTailwindPagination
      :current="currentPage"
      :total="total"
      :per-page="perPage"
      @page-changed="onPageClick($event)"
    />
  </div>
  <table class="table table-dark table-striped">
    <thead>
      <tr>
        <th scope="col">Id</th>
        <th scope="col">Email</th>
        <th scope="col">First Name</th>
        <th scope="col">Last Name</th>
      </tr>
    </thead>
    <tbody>
      <tr v-for="d in data" v-bind:key="d.id">
        <td>{{ d.id }}</td>
        <td>{{ d.email }}</td>
        <td>{{ d.first_name }}</td>
        <td>{{ d.last_name }}</td>
      </tr>
    </tbody>
  </table>
</template>
  • (Line: 20-25) Binding the table data by looping each row.
src/components/Helloworld.vue:
<script>
import "@ocrv/vue-tailwind-pagination/dist/style.css";
import VueTailwindPagination from "@ocrv/vue-tailwind-pagination";
import axios from "axios";
export default {
  components: {
    VueTailwindPagination,
  },
  data() {
    return {
      currentPage: 0,
      perPage: 0,
      total: 0,
      data: [],
    };
  },
  methods: {
    onPageClick(event) {
      this.currentPage = event;
      this.getData(this.currentPage);
    },
    async getData(pageNumber) {
      var response = await axios.get(
        `https://reqres.in/api/users?page=${pageNumber}`
      );
      var responseData = response.data;
      this.currentPage = responseData.page;
      this.perPage = responseData.per_page;
      this.total = responseData.total;
      this.data = response.data.data;
    },
  },
  mounted(){
    this.currentPage = 1;
    this.getData(this.currentPage);
  }
};
</script>
  • (Line: 22-32) The 'getData' method invokes our API, while invoking the API we are passing page number as the query parameter. On receiving the response we are populating table data and also the populating the input properties of the pagination vue component.
  • (Line: 18-21) Inside 'onPageClick' method we update our logic to invoke the API with respect to the page number clicked.
  • (Line: 33-36) Inside 'mounted' method we are fetching API data for the page number '1' for the initial data display.
So that's about the usage of the pagination component in our vue3 application.

Video Session:

 

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information to integrate pagination vue component in the Vue3 application. I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:

Comments

  1. I just had a quick look at this plugin on GitHub; seems pretty solid if you're using tailwind. I can't say that I saw any accessibility roles so I believe it doesn't support screenreaders. Have a look at: https://github.com/OCRVblockchain/vue-tailwind-pagination/blob/main/src/components/VueTailwindPagination/index.vue and search for "aria" for example. Also, the tailwind classes are hardwired in the template so you have no control whatsoever (I suppose that's not a problem if you don't care).

    One positive thing about the plugin is that it doesn't needlessly loop the entire data set and is pretty readable so for that 👍

    I'd like to pitch my pagination as an alternative ;-)
    https://github.com/AgnosticUI/agnosticui/blob/master/agnostic-vue/src/components/Pagination.vue

    It has a lot of configuration options, is accessible (if not I will fix), and support Vue 3. You could apply tailwind if you'd like, or any other CSS framework (although AgnosticUI should suffice). CSS custom properties driven. Please give it a test drive and lmk what you think Naveen!

    ReplyDelete

Post a Comment

Popular posts from this blog

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'

.NET 7 Web API CRUD Using Entity Framework Core

In this article, we are going to implement a sample .NET 7 Web API CRUD using the Entity Framework Core. Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, and desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains programming functions that can be requested via HTTP calls either to fetch or update data for their respective clients. Some of the Key Characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build the REST full services. Install The SQL Server And SQL Management Studio: Let's install the SQL server on our l

ReactJS(v18) JWT Authentication Using HTTP Only Cookie

In this article, we will implement the ReactJS application authentication using the HTTP-only cookie. HTTP Only Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing the JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-ONly cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use the authentication with HTTP-only JWT cookie then we no need to implement the custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To authenticate our client application with JWT HTTP-only cookie, I developed a NetJS(which is a node) Mock API. Check the GitHub link and read the document on G

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se

ReactJS(v18) Authentication With JWT AccessToken And Refresh Token

In this article, we are going to do ReactJS(v18) application authentication using the JWT Access Token and Refresh Token. JSON Web Token(JWT): JSON Web Token is a digitally signed and secured token for user validation. The JWT is constructed with 3 important parts: Header Payload Signature Create ReactJS Application: Let's create a ReactJS application to accomplish our demo. npx create-react-app name-of-your-app Configure React Bootstrap Library: Let's install the React Bootstrap library npm install react-bootstrap bootstrap Now add the bootstrap CSS reference in 'index.js'. src/index.js: import 'bootstrap/dist/css/bootstrap.min.css' Create A React Component 'Layout': Let's add a React component like 'Layout' in 'components/shared' folders(new folders). src/components/shared/Layout.js: import Navbar from "react-bootstrap/Navbar"; import { Container } from "react-bootstrap"; import Nav from "react-boot

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually