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

@graphql-pagination/mongodb

v1.3.1

Published

GraphQL Pagination - MongoDB

Downloads

296

Readme

GraphQL Pagination / MongoDB

Module provides MongoDB DataSource for Graphql Pagination.

Usage

Choose which MongoDb collection field are you going to paginate on. If it's default _id it's expected that is mongo's ObjectId type and needs conversion from string to it via provided ObjectIdCursorEncoderDecoder. Otherwise you don't need to provide cursor and let default cursor decode the cursor.

Initialize the MongoDbDataSource with following config and pass it to dataSourcePager like any other. Use filters to provide additional filtering logic if needed.

import { MongoDbDataSource, ObjectIdCursorEncoderDecoder } from "@graphql-pagination/mongodb";

const mongoDb = mongoClient.db("data");
const dataSource = new MongoDbDataSource<BookType, ObjectId, QueryBooksArgs, QueryBooks_DescArgs>({
    collectionName: "book",
    mongoDb,
    filters: (args) => {
        const filters = [];
        if (args.author) filters.push({ "author": { $eq: args.author } });
        return filters;
    },
});

const cursor = new ObjectIdCursorEncoderDecoder();
// Create pager ideally `dataSourceLoaderPager` within context creation to get benefit of memoization.
// For long lived pager use `dataSourcePager`.
const booksPager = dataSourceLoaderPager({ 
    dataSource, 
    cursor, 
    fetchTotalCountInResolver: false 
    typeName: "Book",
}),

Offset Pagination

If you want to use MongoDb's skip (offset) pagination, you can use MongoDbOffsetDataSource instead of MongoDbDataSource. Implementation also provides sortBy feature.

For offset translation to cursor, it's needed to use OffsetDataSourceWrapper to wrap MongoDbOffsetDataSource.

import { MongoDbOffsetDataSource } from "@graphql-pagination/mongodb";

const mongoDb = mongoClient.db("data");
const ds = new MongoDbOffsetDataSource<BookType, QueryBooksArgs, QueryBooks_DescArgs>({
    collectionName: "book",
    mongoDb,
    filters: (args) => {
        const filters = [];
        if (args.author) filters.push({ "author": { $eq: args.author } });
        return filters;
    },
});
// Always wrap DS with OffsetDataSourceWrapper
const dataSource = new OffsetDataSourceWrapper(ds);

// Create pager ideally `dataSourceLoaderPager` within context creation to get benefit of memoization.
// For long lived pager use `dataSourcePager`.
const booksOffsetPager = dataSourceLoaderPager({ 
    dataSource, 
    fetchTotalCountInResolver: false 
    typeName: "Book",
}),

See fully working example in examples/mongodb.

MongoDbOffsetDataSource Usage

This module can be used to perform both cursor based and offset based pagination on MongoDbDatasources.

Creating a paginated list of Books type

  • In this document we will discuss in more details about how to perform a cursor based pagination on a MongoDb datasource using the MongoDbOffsetDataSource module.

  • Steps to create a pager.

    1. Create a mongoDb.

      import { MongoClient } from 'mongodb';
             
      const options = {} //set the required options
      const mongoClient = new MongoClient("url to the mongoDb",{...options})
      const mongoDb = mongoClient.db("dbName")
    2. Create a datasource using the MongoDbOffsetDataSource .

      const ds = new MongoDbOffsetDataSource<BookType, QueryBooksArgs>({
      	collectionName:"book",
      	mongoDb,
      	sortByFieldName: getSortByField,
      	filters: getFilter
      })

      While creating the “datasource” you can also provide two functions, namely getSortByField and getFilter.

      // This function is used to tell that on what basis the documents must be 
      // sorted and then execute the query. By default "_id" field is used.
      const getSortByField = () => "Title"
             
      // This function is used to return filters on the basis of which you 
      // want to filter out the documents. Must return an array of valid 
      // mongo db conditions.
             
      // The getFilter function here will filter out the book which are written,
      // in the year provided in args.
      const getFilter = (args:QueryBooksArgs) => {
      	const filter = [];
      	if(args.publicYear === null) return filter
      	filters.push({ publicYear : {$eq: args.publicYear} })
      	return filter
      }

      Using the combination of above two functions, we can easily fetch the books written in a particular year sorted alphabetically on the basis of Title. The order of sorting (ascending or descending) can be decided based on the use of forwardResolver or backwardResolver functions present on the pager objects (discussed later)

    3. You should always wrap the object of type MongoDbOffsetDataSource in a OffsetDataSourceWrapper so that offset can be translated to cursor.

      const dataSource = new OffsetDataSourceWrapper(ds);
    4. The next step would be to create a pager Object, while creating the pager object we also get access to the pager type available to be used while defining the schema, so that it can be used while defining the schema, in this case we will have the access to the BookConnection type.

      const bookPager = dataSourcePager<Book, number, QueryBooksArgs>({
      	typeName:"Book",
      	fetchTotalCountInResolver: true,
      	dataSource: datasource,
      	typeDefDirectives: directiveOptions
      })

      This pager object now can be used to perform both cursor based and page based pagination. 😉

    We are now done with creating out pager object, next step would be to use this pager object to get paginated results 🎉.

  • Lets define a GraphQL query to fetch a list of Books. This Query will have an object of BookConnection as return type.

    //This query will return the list of book
    type Query{
    	books(
    		first: Int! = 10
    		page: Int
    		after: String
    		publicYear : Int
    	): BookConnection!
    }
  • Lets write a resolver for this query.

    // Here forward resolver can be used to get the list of books sorted in 
    // ascending order by "Title",
      
    export const Query: QueryResolvers<DataSourceContext> = {
    	books:async (_,args,{bookPager}) => await bookPager.forwardResolver(args);
    }
      
    // To get the list in descending order we can do something like.
    books: async (_,args,{bookPager}) => {
    	const backwardArgs = { ...args, last: args.first, before: args.after };
      return cvePager.backwardResolver(backwardArgs);
    }