npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ottoman-paginate

v1.1.0

Published

A simple pagination library for Ottoman.js

Downloads

9

Readme

Ottoman Paginate 🍨

Introduction

This Plugin, inspired by mongoose-paginate, offers a simple, yet elegant way to implement pagination with Ottoman.js. You can also alter the return value keys directly in the query itself so that you don't need any extra code for transformation.

Installation

yarn add ottoman-paginate

Usage

Add the plugin to a schema and then use the paginate method:

const { model, Schema } = require("ottoman");
const ottomanPaginate = require("ottoman-paginate");

const person = new Schema({
  name: String,
});

person.plugin(ottomanPaginate);

const PersonModel = model("Person", issueSchema);

PersonModel.paginate().then({}); // Usage

Model.paginate([filter], [options], [callback])

Returns a promise

Parameters

  • [filter] {Object} - Filter Query. Documentation
  • [options] {Object} - Options passed to Ottoman's find() function along with other custom options for pagination.
    • [select] {string | string[]} - Fields to return (returns all fields by default). Documentation
    • [sort] {string} - Sort order. Documentation
    • [populate] {string | string[]} - Paths which should be populated with other documents. Documentation
    • [lean] {Boolean}
    • [consistency] {SearchConsistency} - Documentation
    • [noCollection] {undefined | Boolean} - Documentation
    • [populateMaxDeep] {undefined | number} - Documentation
    • [ottomanMetaData=true] {Boolean} - If ottomanMetaData is set to false, it will not include the meta property that is usually present in the response object of Ottoman's find() function.
    • [offset=0] {Number} - Use offset or page to set skip position
    • [page=1] {Number}
    • [limit=10] {Number}
    • [customLabels] {Object} - Add custom labels to manipulate the response data.
    • [pagination] {Boolean} - If pagination is set to false, it will return all docs without adding limit condition. (Default: True)
  • [callback(err, result)] - If specified, the callback is called once pagination results are retrieved or when an error has occurred.

Return value

Promise fulfilled with object having properties:

  • docs {Array} - Array of documents
  • totalDocs {Number} - Total number of documents in collection that match a query
  • limit {Number} - Limit that was used
  • hasPrevPage {Bool} - Availability of previous page.
  • hasNextPage {Bool} - Availability of next page.
  • page {Number} - Current page number.
  • totalPages {Number} - Total number of pages.
  • offset {Number} - Only if specified or default page/offset values were used
  • prevPage {Number} - Previous page number if available or null
  • nextPage {Number} - Next page number if available or null
  • pagingCounter {Number} - The starting index/serial/chronological number of first document in current page. (Eg: if page=2 and limit=10, then pagingCounter will be 11)
  • meta {Object} - Request meta data from Ottoman.
  • paginationMetaData {Object} - Object of pagination meta data (Disabled by default).

The above properties can be renamed by setting customLabels attribute.

Sample Usage

The following returns the first 10 documents from a collection of 100 documents.

const options = {
  page: 1,
  limit: 10,
};

Model.paginate({}, options, function (err, result) {
  // result.docs
  // result.totalDocs = 100
  // result.limit = 10
  // result.page = 1
  // result.totalPages = 10
  // result.hasNextPage = true
  // result.nextPage = 2
  // result.hasPrevPage = false
  // result.prevPage = null
  // result.pagingCounter = 1
  // result.meta
});

With custom return labels

You can change the name of the following attributes

  • totalDocs
  • docs
  • limit
  • page
  • nextPage
  • prevPage
  • hasNextPage
  • hasPrevPage
  • totalPages
  • pagingCounter
  • paginationMetaData

You should pass the names of the properties you wish to change using customLabels object in options. Set the property to false to remove it from the result. Below is a query with custom labels.

const myCustomLabels = {
  totalDocs: "itemCount",
  docs: "itemsList",
  limit: "perPage",
  page: "currentPage",
  nextPage: "next",
  prevPage: "prev",
  totalPages: "pageCount",
  pagingCounter: "slNo",
  paginationMetaData: "paginator",
};

const options = {
  page: 1,
  limit: 10,
  customLabels: myCustomLabels,
};

Model.paginate({}, options, function (err, result) {
  // result.itemsList [here docs becomes itemsList]
  // result.paginator.itemCount = 100 [here totalDocs becomes itemCount]
  // result.paginator.perPage = 10 [here limit becomes perPage]
  // result.paginator.currentPage = 1 [here page becomes currentPage]
  // result.paginator.pageCount = 10 [here totalPages becomes pageCount]
  // result.paginator.next = 2 [here nextPage becomes next]
  // result.paginator.prev = null [here prevPage becomes prev]
  // result.paginator.slNo = 1 [here pagingCounter becomes slNo]
  // result.paginator.hasNextPage = true
  // result.paginator.hasPrevPage = false
});

Other Examples

Using offset and limit:

Model.paginate({}, { offset: 30, limit: 10 }, function (err, result) {
  // result.docs
  // result.totalPages
  // result.limit - 10
  // result.offset - 30
});

With promise:

Model.paginate({}, { offset: 30, limit: 10 }).then(function (result) {
  // ...
});

Adding more options

var filter = {};
var options = {
  select: "title date author",
  sort: { date: "DESC" },
  populate: "author",
  offset: 20,
  limit: 10,
  ottomanMetaData: false,
};

Book.paginate(filter, options).then(function (result) {
  // ...
});

Zero limit

You can use limit=0 to get only the pagination metadata:

Model.paginate({}, { limit: 0 }).then(function (result) {
  // result.docs - empty array
  // result.totalDocs
  // result.limit - 0
});

Fetch all docs without pagination.

If you need to fetch all the documents in the collection without applying a limit. Then set the pagination option to false,

const options = {
  pagination: false,
};

Model.paginate({}, options, function (err, result) {
  // result.docs
  // result.totalDocs = 100
  // result.limit = 100
  // result.page = 1
  // result.totalPages = 1
  // result.hasNextPage = false
  // result.nextPage = null
  // result.hasPrevPage = false
  // result.prevPage = null
  // result.pagingCounter = 1
});

Contribution

If you find an issue with the package or want to add a nice feature, create an issue or submit a PR.

Test

  • Create an .env file with your required variables. Check .example.env to see how it's done.
  • Run the following command.
yarn test

Todo

  • Rewrite with TS and include types