Socket
Socket
Sign inDemoInstall

graphile-build

Package Overview
Dependencies
Maintainers
1
Versions
164
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

graphile-build


Version published
Weekly downloads
29K
increased by0.08%
Maintainers
1
Install size
1.86 MB
Created
Weekly downloads
 

Changelog

Source

4.0.0-rc.6 (2018-08-22)

Bug Fixes

  • error: template string accidentally in quotes (#281) (a9279a0)
  • graphql: handle all long aliases (#272) (92d82da), closes #268
  • ignore-extensions: add pg_depend.classid clause to introspection (#285) (8e68052)
  • mutations: add update and delete mutations for tables lacking primary key (#278) (b28328f)
  • plugins: detect null plugins (#274) (c4f848d), closes #257
  • utils: error when using legacy graphql (#287) (9329fe3), closes #283

Features

  • hstore: add support for the hstore type (#273) (e269c31)
  • makeExtendSchemaPlugin: add support for enum (#269) (0fce134)
  • postgres: add support for postgres inet type (#279) (319d096)
  • query-builder: reference parent query builder on child (#270) (af9ebd9)
  • smart-comments: can edit description of relation fields (#275) (a9efc5c), closes #204
  • smart-comments: can override pgViewUniqueKey for a view (#276) (b5f48c7), closes #178
  • types: beginnings of TypeScriptification (#280) (9fe9b3e)
  • utils: add [@requires](https://github.com/requires)(columns: [...]) directive (#286) (75cd16b)

Readme

Source

graphile-build

graphile-build provides you with a framework to build high-performance extensible GraphQL APIs by combining plugins and using advanced look-ahead features. Plugins may implement best practices (such as the Node interface) or might build parts of your schema automatically (e.g. graphile-build-pg which will automatically generate types and fields based on your PostgreSQL database schema).

An example of an application built on graphile-build is PostGraphile v4+ which allows you to run just one command to instantly get a fully working and secure GraphQL API up and running based on your PostgreSQL database schema.

For in-depth documentation about graphile-build, please see the graphile documentation website.

The below just serves as a limited quick-reference for people already familiar with the library.

Usage

The following runnable example creates a plugin that hooks the 'GraphQLObjectType:fields' event in the system and adds a 'random' field to every object everywhere (including the root Query).

const { buildSchema, defaultPlugins } = require("graphile-build");
// or import { buildSchema, defaultPlugins } from 'graphile-build';

// Create a simple plugin that adds a random field to every GraphQLObject
function MyRandomFieldPlugin(
  builder,
  { myDefaultMin = 1, myDefaultMax = 100 }
) {
  builder.hook("GraphQLObjectType:fields", (fields, build) => {
    const { extend, graphql: { GraphQLInt } } = build;
    return extend(fields, {
      random: {
        type: GraphQLInt,
        args: {
          sides: {
            type: GraphQLInt
          }
        },
        resolve(_, { sides = myDefaultMax }) {
          return (
            Math.floor(Math.random() * (sides + 1 - myDefaultMin)) +
            myDefaultMin
          );
        }
      }
    });
  });
}

// ----------------------------------------

const { graphql } = require("graphql");

(async function() {
  // Create our GraphQL schema by applying all the plugins
  const schema = await buildSchema([...defaultPlugins, MyRandomFieldPlugin], {
    // ... options
    myDefaultMin: 1,
    myDefaultMax: 6
  });

  // Run our query
  const result = await graphql(
    schema,
    `
      query {
        random
      }
    `,
    null,
    {}
  );
  console.log(result); // { data: { random: 4 } }
})().catch(e => {
  console.error(e);
  process.exit(1);
});

Plugins

Plugins can be asynchronous functions (simply define them as async function MyPlugin(builder, options) {...} or return a Promise object).

When a plugin first runs, it should do any of its asynchronous work, and then return. Schema generation itself (i.e. firing of hooks) is synchronous (deliberately).

Most plugins will be of the form:

function MyRandomPlugin(builder) {
  builder.hook("HOOK_NAME_HERE", (
    // 'inputValue' - the value to replace with the return result
    inputValue,
    // 'build' - a frozen collection of utils and stores for this build,
    // not available during the 'build' event
    { extend /* ... */ },
    // 'context' - more information about the current object
    { scope: { isMyRandomObject /* ... */ } /* ... */ }
  ) => {
    if (!isMyRandomObject) {
      // Exit early if this doesn't have the scope we want
      return inputValue;
    }
    return extend(inputValue, {
      // add additional attributes here...
    });
  });
}

Keywords

FAQs

Last updated on 22 Aug 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Packages

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc