Daniel Rearden danielrearden

This document summarizes the schema patterns employed by popular GraphQL APIs, frameworks and service providers. The shown types maybe be incomplete and not completely correct with regard to nullability or type names; however, they should provide a general idea of the capabilities of each provider.

Where appropriate, the shown types illustrate basic features like filtering, sorting and pagination. Providers may expose additional capabilities that are not illustrated in this document.

Find One

AWS Amplify

	const resolvers = {
	Query: {
	customers: (root, args, ctx, info) => {
	return Customer.findMany()
	.resolveInfo(info)
	.execute();
	},
	invoices: (root, args, ctx, info) => {
	return Invoice.findMany()
	.resolveInfo(info)

	query {
	customers(
	where: { firstName: { like: "L%" } }
	orderBy: [{ invoices: { sum: { total: DESC } } }]
	limit: 5
	) {
	id
	firstName
	lastName
	invoices(

	module.exports = {
	db: Knex(...),
	models: 'src/graphql',
	generate: {
	client: {
	// ready-to-use SqlmancerClient instance, no additional initialization needed
	output: 'src/sqlmancer.js'
	},
	typeDefs: {
	output: 'src/graphql/base.graphql'

	/**
	* Here we have type definitions and resolvers for a GraphQL schema. Also shown is the type for the context object passed
	* to each resolver (other types have been omitted for brevity). Each resolver has one issue with it that will cause
	* GraphQL to return an error if that field is requested. In a few sentences, explain what is wrong with each resolver
	* and what you would change to fix it.
	*/

	interface Context {
	db: DB;
	rest: Rest;

	import { createSqlmancerClient, makeSqlmancerSchema } from "sqlmancer";

	const schema = makeSqlmancerSchema({ typeDefs, resolvers });

	import { createSqlmancerClient } from "sqlmancer";
	import { SqlmancerClient } from "./generated";

	const client = createSqlmancerClient<SqlmancerClient>(__filename, knex);