@kamilkisiela/graphql-tools

WebJar for @kamilkisiela/graphql-tools

License

License

MIT
GroupId

GroupId

org.webjars.npm
ArtifactId

ArtifactId

kamilkisiela__graphql-tools
Last Version

Last Version

4.0.6
Release Date

Release Date

Type

Type

jar
Description

Description

@kamilkisiela/graphql-tools
WebJar for @kamilkisiela/graphql-tools
Project URL

Project URL

https://www.webjars.org
Source Code Management

Source Code Management

https://github.com/apollographql/graphql-tools

Download kamilkisiela__graphql-tools

How to add to project

<!-- https://jarcasting.com/artifacts/org.webjars.npm/kamilkisiela__graphql-tools/ -->
<dependency>
    <groupId>org.webjars.npm</groupId>
    <artifactId>kamilkisiela__graphql-tools</artifactId>
    <version>4.0.6</version>
</dependency>
// https://jarcasting.com/artifacts/org.webjars.npm/kamilkisiela__graphql-tools/
implementation 'org.webjars.npm:kamilkisiela__graphql-tools:4.0.6'
// https://jarcasting.com/artifacts/org.webjars.npm/kamilkisiela__graphql-tools/
implementation ("org.webjars.npm:kamilkisiela__graphql-tools:4.0.6")
'org.webjars.npm:kamilkisiela__graphql-tools:jar:4.0.6'
<dependency org="org.webjars.npm" name="kamilkisiela__graphql-tools" rev="4.0.6">
  <artifact name="kamilkisiela__graphql-tools" type="jar" />
</dependency>
@Grapes(
@Grab(group='org.webjars.npm', module='kamilkisiela__graphql-tools', version='4.0.6')
)
libraryDependencies += "org.webjars.npm" % "kamilkisiela__graphql-tools" % "4.0.6"
[org.webjars.npm/kamilkisiela__graphql-tools "4.0.6"]

Dependencies

compile (5)

Group / Artifact Type Version
org.webjars.npm : apollo-utilities jar [1.0.1,2)
org.webjars.npm : apollo-link jar [1.2.3,2)
org.webjars.npm : uuid jar [3.1.0,4)
org.webjars.npm : deprecated-decorator jar [0.1.6,0.2)
org.webjars.npm : iterall jar [1.1.3,2)

Project Modules

There are no modules declared in this project.

toolskit

npm version CI Discord Chat code style: prettier renovate-app badge

This package provides a few useful ways to create a GraphQL schema:

  1. Use the GraphQL schema language to generate a schema with full support for resolvers, interfaces, unions, and custom scalars. The schema produced is completely compatible with GraphQL.js.
  2. Mock your GraphQL API with fine-grained per-type mocking
  3. Automatically stitch multiple schemas together into one larger API

Documentation

Read the docs.

Binding to HTTP

If you want to bind your JavaScript GraphQL schema to an HTTP server, you can use express-graphql.

You can develop your Javascript based GraphQL API with graphql-tools and express-graphql together: One to write the schema and resolver code, and the other to connect it to a web server.

Example

When using graphql-tools, you describe the schema as a GraphQL type language string:

const typeDefs = `
type Author {
  id: ID! # the ! means that every author object _must_ have an id
  firstName: String
  lastName: String
  """
  the list of Posts by this author
  """
  posts: [Post]
}

type Post {
  id: ID!
  title: String
  author: Author
  votes: Int
}

# the schema allows the following query:
type Query {
  posts: [Post]
}

# this schema allows the following mutation:
type Mutation {
  upvotePost (
    postId: ID!
  ): Post
}

# we need to tell the server which types represent the root query
# and root mutation types. We call them RootQuery and RootMutation by convention.
schema {
  query: Query
  mutation: Mutation
}
`;

export default typeDefs;

Then you define resolvers as a nested object that maps type and field names to resolver functions:

const resolvers = {
  Query: {
    posts() {
      return posts;
    },
  },
  Mutation: {
    upvotePost(_, { postId }) {
      const post = find(posts, { id: postId });
      if (!post) {
        throw new Error(`Couldn't find post with id ${postId}`);
      }
      post.votes += 1;
      return post;
    },
  },
  Author: {
    posts(author) {
      return filter(posts, { authorId: author.id });
    },
  },
  Post: {
    author(post) {
      return find(authors, { id: post.authorId });
    },
  },
};

export default resolvers;

At the end, the schema and resolvers are combined using makeExecutableSchema:

import { makeExecutableSchema } from '@graphql-tools/schema';

const executableSchema = makeExecutableSchema({
  typeDefs,
  resolvers,
});

GraphQL-Tools schema can be consumed by frameworks like Apollo GraphQL or express-graphql For example

var express = require('express');
var { graphqlHTTP } = require('express-graphql');

var app = express();
app.use('/graphql', graphqlHTTP({
  schema: executableSchema,
  graphiql: true,
}));
app.listen(4000);
console.log('Running a GraphQL API server at http://localhost:4000/graphql');

This example has the entire type definition in one string and all resolvers in one file, but you can combine types and resolvers from multiple files and objects, as documented in the modularizing type definitions and merging resolvers section of the docs.

Contributions

Contributions, issues and feature requests are very welcome. If you are using this package and fixed a bug for yourself, please consider submitting a PR!

Maintainers

org.webjars.npm

Apollo GraphQL

A community building flexible open source tools for GraphQL.

Versions

Version
4.0.6