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-operation-to-pojo

v1.0.10

Published

Converts GraphQL operations to plain old JS objects (POJOs), ready to to be serialized to JSON

Downloads

351

Readme

graphql-operation-to-pojo

Converts GraphQL operations to plain old JS objects (POJOs), ready to to be serialized to JSON.

This can be used to parse the info argument (GraphQLResolveInfo) passed to GraphQL resolvers.

Installation

npm i -S graphql-operation-to-pojo

Or:

yarn add graphql-operation-to-pojo

Usage

myResolver(obj, args, context, info) {
    const queryPOJO = graphqlOperationToPOJO(info)
    ...
}

There is also a helper function to serialize the result to a JSON string:

const jsonString = graphqlOperationToJSON(info)

(This is equivalent to calling JSON.stringify(graphqlOperationToPOJO(info)))

Options

Options can optionally be passed as a second argument, e.g.:

graphqlOperationToPOJO(info, {
    includeFieldPath: true,
    includeReturnType: true,
})

Available options:

  • includeFieldPath: boolean (defaults to false)

    If true, a path property will be added to each field object and set to the path to the field from the root of the query, e.g. 'hero.name'

  • includeReturnTypes: boolean (defaults to false)

    If true, the return type of each field will be included in the result.

Tip: When using includeReturnTypes, you can use getNamedType() from graphql.js to strip any wrapping non-null or list types and get the underlying type. For example:

import { getNamedType } from 'graphql'
...
/*
Suppose we're running a query that returns a list of users:

  type Query {
    users: [User!]!
  }
*/
const returnType = getNamedType(queryPojo.fields[0].returnType)
console.log(returnType.toString())
// Output: 'User'

Examples

Given the query:

query {
    hero(episode: NEWHOPE) {
        name
        friends {
            name
            appearsIn
        }
    }
}

graphqlOperationToPOJO will return:

{
    "operation": "query",
    "fields": [
        {
            "name": "hero",
            "fields": [
                {
                    "name": "name"
                },
                {
                    "name": "friends",
                    "fields": [
                        {
                            "name": "name"
                        },
                        {
                            "name": "appearsIn"
                        }
                    ]
                }
            ],
            "arguments": {
                "episode": "NEWHOPE"
            }
        }
    ]
}

Aliases

If the query contains aliases, the field object will include an alias property, e.g.:

{
    hero(episode: NEWHOPE) {
        heroName: name
    }
}
{
    "operation": "query",
    "fields": [
        {
            "name": "hero",
            "fields": [
                {
                    "name": "name",
                    "alias": "heroName"
                }
            ],
            "arguments": {
                "episode": "NEWHOPE"
            }
        }
    ]
}

Fragments

Type conditions for fragments are stored in a fragmentType property, e.g.:

{
    character(id: "1000") {
        ... on Human {
            id
            name
            friends {
                id
            }
        }
        ... on Droid {
            name
            friends {
                name
            }
        }
    }
}
{
    "operation": "query",
    "fields": [
        {
            "name": "character",
            "fields": [
                {
                    "name": "id",
                    "fragmentType": "Human"
                },
                {
                    "name": "name",
                    "fragmentType": "Human"
                },
                {
                    "name": "friends",
                    "fragmentType": "Human",
                    "fields": [
                        {
                            "name": "id"
                        }
                    ]
                },
                {
                    "name": "name",
                    "fragmentType": "Droid"
                },
                {
                    "name": "friends",
                    "fragmentType": "Droid",
                    "fields": [
                        {
                            "name": "name"
                        }
                    ]
                }
            ],
            "arguments": {
                "id": "1000"
            }
        }
    ]
}