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-fields-mongo

v1.0.2

Published

This library create field projection from GraphQL query

Downloads

2

Readme

GraphQL Fields mongo ( Version 4.4 )

This library create field projection from GraphQL query

Why using this?

There are many libraries can do the same function. However, starting in MongoDB 4.4, the Path Collision Restrictions are introduced . And it is illegal to project an embedded document with any of the embedded document's fields:

db.inventory.find({}, { size: 1, "size.uom": 1 }); // Invalid starting in 4.4
  • And this library is created to remove the collision.
  • This library can work with dataloader also

Install

npm install graphql-fields-mongo

How to

Please see the following examples

Example 1: simplest usecase

Given the following query

query user {
  user(id: 123) {
    id
    address
    info {
      firstName
      lastName
    }
  }
}
const { createSelectedFields } = require('graphql-fields-mongo');

resolve(parent, args, context, info){
  const selectedFields = createSelectedFields(info); // [ 'id', 'address', 'info.firstName', 'info.lastName' ]
}

Example 2: Get more fields

Given the following query

query user {
  user(id: 123) {
    id
    address
    info {
      firstName
      lastName
    }
  }
}
const { createSelectedFields } = require('graphql-fields-mongo');

resolve(parent, args, context, info){
  // Now you like to get more fields for further resolve: `timezone`, and `info` object
  const selectedFields = createSelectedFields(info, { additionalFields: ['info', 'address', 'timezone'] }); // [ 'id', 'info', 'timezone' ]
}

Example 3: Get child path

Given the following query

query purchase {
  purchase(id: 123) {
    id
    buyer {
      id
      address
      info {
        firstName
        lastName
      }
    }
    product {
      id
      # ...others
    }
  }
}
const { createSelectedFields } = require('graphql-fields-mongo');

resolve(parent, args, context, info){
  // Now you like to get selected fields of `buyer`
  const selectedFields = createSelectedFields(info, { path: 'buyer' }); // [ 'id', 'address', 'info.firstName', 'info.lastName' ]

  // OR with additionalFields
const selectedFields2 = createSelectedFields(info, {
  path: 'buyer', additionalFields: ['info', 'address', 'timezone'],
}); // [ 'id', 'info', 'timezone' ]
}

Example 4: returnTypes

By the default the return result will be an array of projected fields. But you can also get the string or object

query user {
  user(id: 123) {
    id
    address
    info {
      firstName
      lastName
    }
  }
}
const { createSelectedFields } = require('graphql-fields-mongo');

resolve(parent, args, context, info){
  const resultArray1 = createSelectedFields(info); // [ 'id', 'address', 'info.firstName', 'info.lastName' ]
  const resultArray2 = createSelectedFields(info, { returnType : 'array' }); // [ 'id', 'address', 'info.firstName', 'info.lastName' ]
  const resultString = createSelectedFields(info, { returnType : 'string' } ); // 'id address info.firstName info.lastName'
  const resultObject = createSelectedFields(info, { returnType : 'object' }); // { id: 1, address: 1, 'info.firstName': 1, 'info.lastName': 1 }
}

Example 5: Using with Dataloader

query purchase {
  purchase(id: 123) {
    id
    buyer {
      id
      address
      info {
        firstName
        lastName
      }
    }
    products {
      id
      sku
      name
      price
    }
  }
}
const { createSelectedFields, createMergedSelectedFields } = require('graphql-fields-mongo');

// This is an example with Apollo Federation, but you can run with any resolvers
__resolveReference(parent, context, info) {
  const { loaders } = context;
  const selectedFields = createSelectedFields(info);
  return loaders.product.load(JSON.stringify({ id: parent.id, selectedFields }));
}

// The implementation of `loaders.product()`
async function batchProducts(keys) {
  const { ids: productIds, selectedFields } = createMergedSelectedFields(keys);
  const products = await Product.find({ _id: { $in: productIds } })
    .select(selectedFields)
    .lean();

  // Don't forget mapping results
  // ...

  return products;
}

The function createMergedSelectedFields() supports the following options: