Daniel Rearden danielrearden

## example.graphql
query {
  viewer {
    gists (first: 100, orderBy: {field: CREATED_AT, direction: DESC} ) {
      edges {
        node {
          createdAt
          description
          name
          pushedAt
          stargazers (first: 100) {

## createJunctionConnectionLoaderClass.ts

import DataLoader from 'dataloader';
import _ from 'lodash';
import {
  sql,
  DatabaseConnectionType,
  IdentifierSqlTokenType,
  PrimitiveValueExpressionType,
  SqlSqlTokenType,
  SqlTokenType,

## createConnectionLoaderClass.ts
/* eslint-disable @typescript-eslint/ban-types, @typescript-eslint/explicit-module-boundary-types, fp/no-this, max-nested-callbacks */

import DataLoader from 'dataloader';
import _ from 'lodash';
import {
  sql,
  DatabaseConnectionType,
  IdentifierSqlTokenType,
  PrimitiveValueExpressionType,
  SqlSqlTokenType,

## test.ts
/**
 * 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;

## schema-patterns.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                danielrearden
                / schema-patterns.md
            
            
              Last active
              June 30, 2020 04:24
            
              
                Schema Patterns by Provider
              
          
    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


## 1-sqlmancer.config.js
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'

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

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

## sqlmancer.sh
sqlmancer generate ./some/glob/**/*.graphql ./generated.ts

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

## index.ts
const apollo = new ApolloServer({ schema })
	query {
	viewer {
	gists (first: 100, orderBy: {field: CREATED_AT, direction: DESC} ) {
	edges {
	node {
	createdAt
	description
	name
	pushedAt
	stargazers (first: 100) {

	import DataLoader from 'dataloader';
	import _ from 'lodash';
	import {
	sql,
	DatabaseConnectionType,
	IdentifierSqlTokenType,
	PrimitiveValueExpressionType,
	SqlSqlTokenType,
	SqlTokenType,
	/* eslint-disable @typescript-eslint/ban-types, @typescript-eslint/explicit-module-boundary-types, fp/no-this, max-nested-callbacks */

	import DataLoader from 'dataloader';
	import _ from 'lodash';
	import {
	sql,
	DatabaseConnectionType,
	IdentifierSqlTokenType,
	PrimitiveValueExpressionType,
	SqlSqlTokenType,
	/**
	* 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;
	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'
	import { createSqlmancerClient } from "sqlmancer";
	import { SqlmancerClient } from "./generated";

	const client = createSqlmancerClient<SqlmancerClient>(__filename, knex);
	query {
	customers(
	where: { firstName: { like: "L%" } }
	orderBy: [{ invoices: { sum: { total: DESC } } }]
	limit: 5
	) {
	id
	firstName
	lastName
	invoices(