graphql-directive-connection

This package generates relay connections by marking fields with a @connection directive, and then passing your SDL through applyConnectionTransform.

Example

1import sqlDirective from 'graphql-to-sql'
2import privateDirective from 'graphql-directive-private'
3import connectionDirective from 'graphql-directive-connection'
4import { makeExecutableSchema } from '@graphql-tools/schema'
5
6const { generateSql } = sqlDirective('sql')
7const { privateDirectiveTransform } = privateDirective('private')
8const { connectionDirectiveTransform } = connectionDirective('connection')
9
10const typeDefs = `
11  directive @connection on FIELD_DEFINITION
12  directive @private on OBJECT | FIELD_DEFINITION
13
14  type User {
15    userId: Int @sql(type: "BINARY(16)", primary: true)
16    password: String @sql(type: "VARCHAR(255)", primary: true) @private
17    
18    # Tag the field with @connection. Its return type will be replaced with PostConnection.
19    posts: [Post!]! @connection
20  }
21
22  type Post {
23    postId: Int @sql(type: "BINARY(16)", primary: true)
24  }
25
26  type Query {
27    user: User
28  }
29`
30
31export const sql = generateSql({typeDefs}, {
32  databaseName: 'public',
33  tablePrefix: 'test_',
34  dbType: 'mysql',
35})
36
37let schema = makeExecutableSchema({
38  typeDefs
39})
40
41schema = privateDirectiveTransform(schema)
42schema = connectionDirectiveTransform(schema)
43
44export default schema

It will:

• Create the needed Connection and Edge object types.
• Reassign the type of marked fields to the Connection type.
• Remove any @connection directives.
• Generate the PageInfo object type if it hasn't been defined.
• Throw errors if the generated Connection and Edge types have a name conflict with types already defined in your SDL.
• Leave everything else in your SDL untouched.

These types will be added to your schema:

1type PageInfo {
2  hasNextPage: Boolean!
3  hasPreviousPage: Boolean!
4  startCursor: String
5  endCursor: String
6}
7
8type PostEdge {
9  cursor: String!
10  node: Post
11}
12
13type PostConnection {
14  totalCount: Int!
15  edges: [PostEdge]
16  pageInfo: PageInfo!
17}

cacheControl

By default, the cacheControl directives are not generated on Edge object types and inside connection fields which results in cache arguments being completely ignored. Enabling defaultMaxAge for all types/fields across your GraphQL implementation partially solve the problem, however it might not be the best options. It is possible to enable cacheControl directive support by passing a useCacheControl: true flag to applyConnectionTransform function. The package will then use the largest maxAge across the connection fields with custom types and apply it to edges and pageInfo fields along with the Edge type.