Paginating Using Infinite Results


You wish to paginate through server-side data with a “Load More” button, which just keeps appending more data until no more data is available.


Let’s start by looking at how the item table is rendered with the ng-repeat Directive.

<div ng-controller="PaginationCtrl">
  <table class="table table-striped">
      <tr ng-repeat="item in pagedItems">
      <td colspan="3">
        <button class="btn" href="#" ng-class="nextPageDisabledClass()"
          ng-click="loadMore()">Load More</button>

The controller uses the same Item Service as used for the previous recipe and handles the logic for the “Load More” button.

app.controller("PaginationCtrl", function($scope, Item) {

  $scope.itemsPerPage = 5;
  $scope.currentPage = 0;
  $ =;
  $scope.pagedItems = Item.get($scope.currentPage*$scope.itemsPerPage,

  $scope.loadMore = function() {
    var newItems = Item.get($scope.currentPage*$scope.itemsPerPage,
    $scope.pagedItems = $scope.pagedItems.concat(newItems);

  $scope.nextPageDisabledClass = function() {
    return $scope.currentPage === $scope.pageCount()-1 ? "disabled" : "";

  $scope.pageCount = function() {
    return Math.ceil($$scope.itemsPerPage);


You can find the complete example on github.


The solution is actually pretty similar to the previous recipe and uses a controller only again. The $scope.pagedItems is retrieved initially to render the first five items.

When pressing the “Load More” button we fetch another set of items incrementing the currentPage to change the offset of the Item.get function. The new items will be concatenated with the existing items using the Array concat function. The changes to pagedItems will be automatically rendered by the ng-repeat directive.

The nextPageDisabledClass checks whether there is more data available by calculating the total number of pages in pageCount and comparing that to the current page.