> 🌿 Combines schemas and types to help you modularize your GraphQL service
> 🌿 Combines schemas and types to help you modularize your GraphQL service
GraphQL is awesome, but there isn't yet a standardized way to break up schemas
in a way that makes sense. By enforcing a simple standard (exporting certain variables) on all your schema
files, you can break the service up in a way that makes sense for your project.
We believe this system allows you to make very few boilerplate changes to extend
your service while also being very explicit—we don't like unnecessary magic.
ℹ️ This is just a very thin wrapper extending/replacing makeExecutableSchema.
See graphql-tools for more documentation.
All your schema files can export typeDefs, resolvers, andschemaDirectives. All are optional.
To add functionality, each file may:
- Extend a root type: Query and/or Mutation
- Add or extend custom typesD
- Add resolvers for the types
- Add a custom scalar/enum
- Example usage
- Read the graphql-tools
documentation
more more information
- Add a custom schema directive
- Example usage
- Read the graphql-tools
documentation
more more information
``js
// Example Users schema file
import { fetchUser, fetchUsers } from './users';
export const typeDefs = / GraphQL /
type User {
lastSeen: Timestamp
name: String
}
# Extend the root types to expose logic...
extend type Query {
user(id: ID!): User
users: [User]
};
export const resolvers = {
Query: {
user: (_, { id }) => fetchUser(id),
users: () => fetchUsers()
}
};
`
Then, import the schema parts into a single file and create a root schema:
`js
import {
combineSchemaDefinitions,
makeExecutableSchema
} from 'create-root-schema';
import * as device from './device';
import * as notification from './notification';
import * as user from './user';
// NOTE: Choose one of these options…
// - option 1: get the combined schema:
export default combineSchemaDefinitions([device, notification, user]);
// - option 2: both combine the schema and convert to an executable schema:
export default makeExecutableSchema([device, notification, user]);
`
`js
// ./schemas/index.js
import { combineSchemaDefinitions } from 'create-root-schema';
import * as device from './device';
import * as notification from './notification';
import * as user from './user';
export default combineSchemaDefinitions([brand, device, notification, user]);
`
`js
// ./index.js
import { ApolloServer, gql } from 'apollo-server-express';
import express from 'express';
import schema from './schemas';
const app = express();
const server = new ApolloServer(schema);
server.applyMiddleware({ app });
app.listen({ port: 4000 }, () =>
console.log(🚀 Server ready at http://localhost:4000${server.graphqlPath})`
);
`js
// ./schemas/index.js
import { combineSchemaDefinitions } from 'create-root-schema';
import * as device from './device';
import * as notification from './notification';
import * as user from './user';
export default combineSchemaDefinitions([brand, device, notification, user]);
`
`js
import { GraphQLServer } from 'graphql-yoga';
import schema from './schemas';
const server = new GraphQLServer(schema);
server.start(() => console.log('Server is running on localhost:4000'));
`
This is just a thin wrapper around makeExecutableSchema. Any options passed as the second argument will be forwarded directly to makeExecutableSchema.
`js
import { makeExecutableSchema } from 'create-root-schema';
// See graphql-tools docs for more information`
makeExecutableSchema([...schemas], { allowUndefinedInResolve: false });
With Yarn or npm installed, run:
`
yarn add create-root-schema
MIT