The simplest solution for pagination in Angular.
- Demo
- Quick Start
- Simple Example
- API
- Styling
- Server-Side Paging
- Multiple Instances
- FAQ
- Building from source
- License
Check out the live demo here: http://michaelbromley.github.io/ngx-pagination/
Play with it on StackBlitz here: https://stackblitz.com/edit/angular-e1f9hq
npm install ngx-pagination --save
This library is built to work with Angular 13+. If you need to support an earlier version of Angular, please use v5.x.
// app.module.ts
import {NgModule} from '@angular/core';
import {BrowserModule} from '@angular/platform-browser';
import {NgxPaginationModule} from 'ngx-pagination'; // <-- import the module
import {MyComponent} from './my.component';
@NgModule({
imports: [BrowserModule, NgxPaginationModule], // <-- include it in your app module
declarations: [MyComponent],
bootstrap: [MyComponent]
})
export class MyAppModule {}// my.component.ts
import {Component} from '@angular/core';
@Component({
selector: 'my-component',
template: `
<ul>
<li *ngFor="let item of collection | paginate: { itemsPerPage: 10, currentPage: p }"> ... </li>
</ul>
<pagination-controls (pageChange)="p = $event"></pagination-controls>
`
})
export class MyComponent {
p: number = 1;
collection: any[] = someArrayOfThings;
}The PaginatePipe should be placed at the end of an NgFor expression. It accepts a single argument, an object conforming
to the PaginationInstance interface. The following config options are available:
<some-element *ngFor="let item of collection | paginate: { id: 'foo',
itemsPerPage: pageSize,
currentPage: p,
totalItems: total }">...</some-element>itemsPerPage[number] - required The number of items to display on each page.currentPage[number] - required The current (active) page number.id[string] If you need to support more than one instance of pagination at a time, set theidand ensure it matches the id attribute of thePaginationControlsComponent/PaginationControlsDirective(see below).totalItems[number] The total number of items in the collection. Only useful when doing server-side paging, where the collection size is limited to a single page returned by the server API. For in-memory paging, this property should not be set, as it will be automatically set to the value ofcollection.length.
This a default component for displaying pagination controls. It is implemented on top of the PaginationControlsDirective, and has a pre-set
template and styles based on the Foundation 6 pagination component. If you require a more
customised set of controls, you will need to use the PaginationControlsDirective and implement your own component.
<pagination-controls id="some_id"
(pageChange)="pageChanged($event)"
(pageBoundsCorrection)="pageChanged($event)"
maxSize="9"
directionLinks="true"
autoHide="true"
responsive="true"
previousLabel="Previous"
nextLabel="Next"
screenReaderPaginationLabel="Pagination"
screenReaderPageLabel="page"
screenReaderCurrentLabel="You're on page">
</pagination-controls>id[string] If you need to support more than one instance of pagination at a time, set theidand ensure it matches the id set in the PaginatePipe config.pageChange[event handler] The expression specified will be invoked whenever the page changes via a click on one of the pagination controls. The$eventargument will be the number of the new page. This should be used to update the value of thecurrentPagevariable which was passed to thePaginatePipe.pageBoundsCorrection[event handler] The expression specified will be invoked when thecurrentPagevalue is found to be out-of-bounds (e.g. the collection size was reduced). The$eventargument will be the number of the closest valid page.maxSize[number] Defines the maximum number of page links to display. Default is7. Minimum is5.directionLinks[boolean] If set tofalse, the "previous" and "next" links will not be displayed. Default istrue.autoHide[boolean] If set totrue, the pagination controls will not be displayed when all items in the collection fit onto the first page. Default isfalse.responsive[boolean] If set totrue, individual page links will not be displayed on small screens. Default isfalse.previousLabel[string] The label displayed on the "previous" link.nextLabel[string] The label displayed on the "next" link.screenReaderPaginationLabel[string] The word for "Pagination" used to label the controls for screen readers.screenReaderPageLabel[string] The word for "page" used in certain strings generated for screen readers, e.g. "Next page".screenReaderCurrentLabel[string] The phrase indicating the current page for screen readers, e.g. "You're on page ".
The PaginationControlsDirective is used to build components for controlling your pagination instances. The directive selector is pagination-template, either as an element or an attribute.
It exports an API named "paginationApi", which can then be used to build the controls component.
It has the following inputs and outputs:
@Input() id: string;
@Input() maxSize: number;
@Output() pageChange: EventEmitter<number>;
@Output() pageBoundsCorrection: EventEmitter<number>;Here is an example of how it would be used to build a custom component:
<pagination-template #p="paginationApi"
(pageChange)="pageChange.emit($event)"
(pageBoundsCorrection)="pageBoundsCorrection.emit($event)">
<div class="pagination-previous" [class.disabled]="p.isFirstPage()">
<a *ngIf="!p.isFirstPage()" (click)="p.previous()"> < </a>
</div>
<div *ngFor="let page of p.pages" [class.current]="p.getCurrent() === page.value">
<a (click)="p.setCurrent(page.value)" *ngIf="p.getCurrent() !== page.value">
<span>{{ page.label }}</span>
</a>
<div *ngIf="p.getCurrent() === page.value">
<span>{{ page.label }}</span>
</div>
</div>
<div class="pagination-next" [class.disabled]="p.isLastPage()">
<a *ngIf="!p.isLastPage()" (click)="p.next()"> > </a>
</div>
</pagination-template>The key thing to note here is #p="paginationApi" - this provides a local variable, p (name it however you like), which can be used in the
template to access the directive's API methods and properties, which are explained below:
pages[{ label: string, value: any }[]] Array of page objects containing the page number and label.maxSize[number] Corresponds to the value ofmaxSizewhich is passed to the directive.getCurrent()[() => number] Returns the current page number.setCurrent(val)[(val: number) => void] Triggers thepageChangeevent with the page number passed asval.previous()[() => void] Sets current page to previous, triggering thepageChangeevent.next()[() => void] Sets current page to next, triggering thepageChangeevent.isFirstPage()[() => boolean] Returns true if the current page is the first page.isLastPage()[() => boolean] Returns true if the current page is the last pagegetLastPage()[() => number] Returns the page number of the last page.getTotalItems()[() => number] Returns the total number of items in the collection.
For a real-world implementation of a custom component, take a look at the source for the PaginationControlsComponent.
The PaginationControlsComponent can be styled by simply overriding the default styles. To overcome Angular's view encapsulation, you may need to use the ::ng-deep operator to target it (depending on the type of encapsulation your component is using).
To avoid specificity issues, just add your own custom class name to the element, which will allow your styles to override the defaults:
// head
<style>
.my-pagination ::ng-deep .ngx-pagination .current {
background: red;
}
</style>
// body
<pagination-controls class="my-pagination"><pagination-controls>In many cases - for example when working with very large data-sets - we do not want to work with the full collection in memory, and use some kind of server-side paging, where the server sends just a single page at a time.
This scenario is supported by ngx-pagination by using the totalItems config option.
Given a server response json object like this:
{
"count": 14453,
"data": [
{ /* item 1 */ },
{ /* item 2 */ },
{ /* item 3 */ },
{ /* ... */ },
{ /* item 10 */ }
]
}
we should pass the value of count to the PaginatePipe as the totalItems argument:
<li *ngFor="let item of collection | paginate: { itemsPerPage: 10, currentPage: p, totalItems: res.count }">...</li>This will allow the correct number of page links to be calculated. To see a complete example of this (including
using the async pipe), see the demo.
It is possible to have any number of pagination pipe/controls pairs in the same template. To do this, just make use of the "id" attribute:
<ul>
<li *ngFor="let item of collection | paginate: { itemsPerPage: 10, currentPage: p1, id: 'first' }"> ... </li>
</ul>
<pagination-controls (pageChange)="p1 = $event" id="first"></pagination-controls>
<ul>
<li *ngFor="let item of collection | paginate: { itemsPerPage: 10, currentPage: p2, id: 'second' }"> ... </li>
</ul>
<pagination-controls (pageChange)="p2 = $event" id="second"></pagination-controls>You can even have dynamically-generated instances, e.g. within an ngFor block:
export class MyComponent {
p: number[] = [];
}<div *ngFor="let id of [1, 2]; let i = index;">
<ul>
<li *ngFor="let item of collection | paginate: { itemsPerPage: 10, currentPage: p[i], id: id }">{{ item }}</li>
</ul>
<pagination-controls (pageChange)="p[i] = $event" [id]="id"></pagination-controls>
</div>A common issue is that people have trouble combining some kind of filter pipe with the paginate pipe. The typical symptom is that only the contents of the current page are filtered. The reason is that the paginate pipe must come after the filter pipe:
<ul>
<li *ngFor="let item of collection | paginate: config | filter: queryString">WRONG</li> <-- This will not work as expected
</ul>
<ul>
<li *ngFor="let item of collection | filter: queryString | paginate: config">CORRECT</li>
</ul>If you need to use the index of the *ngFor in combination with pagination pipe, the index should be declared after the pagination pipe:
<ul>
<li *ngFor="let item of collection; let i = index | paginate: config">WRONG</li>
</ul>
<ul>
<li *ngFor="let item of collection | paginate: config; let i = index">CORRECT</li>
</ul>Using the index variable exposed by ngFor will always give you the index of the items relative to the current page. For example, if you have 10 items per page, you might expect the first item on page 2 to have an index value of 10, whereas you will find the index value to be 0. This is because ngFor has no knowledge of the pagination, it only ever knows about the 10 items of the current page.
However, the absolute index can be calculated according to the following formula:
absoluteIndex(indexOnPage: number): number {
return this.itemsPerPage * (this.currentPage - 1) + indexOnPage;
}In a template this would look something like:
<ul>
<li *ngFor="let item of collection | paginate: { currentPage: currentPage, itemsPerPage: itemsPerPage }; let i = index">
{{ itemsPerPage * (currentPage - 1) + i }}
</li>
</ul>Requires globally-installed node (tested with v5.x) & npm.
npm install
npm run test
npm run build
After running npm run build, the final output of the lib (which gets published to npm) is in the /dist/ngx-pagination folder.
To build the docs, run npm run build:docs, or serve them in dev mode with npm run start.
MIT
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent