gql-queries-autogenerator

Autogenerate simplest client queries from graphql types.

What does it do?

It converts graphql types to appropriate queries with javascript syntax like so:

from:

1type MessageSubType{
2  author: String!,
3  value: String!
4}

to:

1export const messageSubType = gql`
2    query MessageSubType {

3        author,
4        value
5    }
6`;

Installation:

1npm i -D gql-queries-generator

How to use?

Graphql server should be running on port 8000

via cli:

Generate queries to target.js:

1gq-gen ./target.js

or the same without installation:

1npx gql-queries-autogenerator ./target.js

Possible advanced options:

• --template - specifies template file name that will be used to generate the target file
• -p - number port of graphql server if it differs from the default one

via programming (more powerfull):

Programming usage allows to specify more options

1const createQueries = require('gql-queries-generator').createQueries;
2
3// or `import {createQueries} from 'gql-queries-generator';`
4
5createQueries('d.js', {
6    template: './template.js',
7    // another options (look up below)
8})

Possible options:

• port - number - number port of graphql server if it differs from the 8000

• host - string - host name of graphql server if it differs from the 127.0.0.1

• template - string - template for the generated file

• exclude - string[] - list of types to ignore when generating

• include - {base: string[], complex: {[key: QueryName]: args: RootFieldName, fields: {[key: fieldName]: fields[]}}} - by default, gql-queries-generator generates queries only for basic types. Such requests will contain one type and a description of all its fields. In this case, such a request will ignore nested types. The include option allows you to describe more complex queries that the graphql server returns. For example:

  1include: {
  2    base: [],
  3    complex: {
  4        posts: {
  5            args: ["user"],
  6            fields: {
  7                by: ["id"]
  8            }
  9        }
  10    }
  11}

  will generate:

  1export const postType = gql`
  2    query PostType {
  3        posts (user: $user) {
  
  4            id,
  5            by {
  
  6                id,
  7            },
  
  8            time,
  
  9            value,
  
  10            files,
  
  11            likesCount,
  12            rated
  13        }
  14    }
  15`

  where PostType is operation name automatically picked up from the server

---

Advanced usage:

Typescript support:

template option allows you to specify any file extension, including .ts. In the latter case, the QueryString type will be automatically added to the description of queries and according string annotation like this:

1export const likeApply = gql`
2    mutation LikeMutation {
3        likeApply(postId: $postId){
4            increased
5        }
6    }
7` as QueryString<'LikeMutation'>;

It is assumed that QueryString has the following description:

1type QueryString<T extends string> = `\n    ${'mutation'|'query'} ${T}${string}`

but its may be overriten inside template (look up template option). If templte does not contains QueryString type, its'll be added automatically (template must have also .ts extension. Else assumed QueryString type as global type)

Further the QueryString<T> may be use to integrate the tool with graphql-types-generator via extracting according type from QueryTypes (look up graphql-types-generator documentation) or with @graphql-codegen/typescript-operations, but in the last case its require some additional tuning.