Document a GraphQL API

GraphqlGraphql Js

Graphql Problem Overview


With REST we can use Swagger, RAML or other technologies to document our API and generate an HTML documentation that our consumers can read without any need of interaction with the servers.

Does something similar exist for GraphQL? Is there any way to generate a documentation of resources and properties?

Graphql Solutions


Solution 1 - Graphql

It looks like there is now https://www.npmjs.com/package/graphql-docs

> Dynamically generated documentation explorer for GraphQL schemas. It aims to provide a better overview of a schema than GraphiQL, but without querying features.

enter image description here

You can also generate a static documentation file based on a schema file or GraphQL endpoint:

npm install -g graphql-docs
graphql-docs-gen http://GRAPHQL_ENDPOINT documentation.html

Solution 2 - Graphql

To my knowledge there is no tool yet that automatically generates HTML documentation for a GraphQL API, but I've found GraphiQL to be even more useful than any API documentation in HTML that I've seen.

GraphiQL lets you interactively explore the schema of a GraphQL server and run queries against it at the same time. It has syntax highlighting, autocompletion, and it even tells you when your query is invalid without executing it.

If you're looking for static documentation, I've found it pretty convenient to read the schema in GraphQL schema language. Thanks to another great feature of GraphQL - schema introspection - you can easily print the schema for any server you have access to. Simply run the introspection query against the server and then print the resulting introspection schema like so (using graphql-js):

var graphql = require('graphql');
var introspectionSchema = {}; // paste schema here
console.log(graphql.printSchema(graphql.buildClientSchema(introspectionSchema)));

The result will look something like this:

# An author
type Author {
  id: ID!

  # First and last name of the author
  name: String
}

# The schema's root query type
type Query {

  # Find an author by name (must match exactly)
  author(name: String!): Author
}

Solution 3 - Graphql

I found Static page generator for documenting GraphQL Schema. GitHub link.

HTML export looks like this.

GitHub GraphQL doc example

Solution 4 - Graphql

Actually Graphql is quite self documented with Facebook's built-in Graphiql or the 3rd party tool like Altair because the queries/mutations are listed and return types are also shown there.

One place I found need doc is the input query parameter which might require specific format. This can be achieved by adding a comment on top of those arguments.

  type Query {
      eventSearch(
        # comma separated location IDs. (eg: '5,12,27')
        locationIds: String,
        # Date Time should be ISO 8601: 'YYYY-DD-MM HH:mm:ss'. (eg: '2018-04-23 00:00:00')
        startDateTime: String!,
        endDateTime: String!): [Event]
  }

It will be like below:

Graphiql:

Graphiql

Altair:

Altair

Solution 5 - Graphql

Another recent tool is SpectaQL. The output can look like this. Quoting from the README:

> Autogenerate static GraphQL API documentation. > > SpectaQL is a Node.js library that generates static documentation for a GraphQL schema using a variety of options: > 1. From a live endpoint using the introspection query. > 1. From a file containing an introspection query result. > 1. From a file, files or glob leading to the schema definitions in SDL. > > The goal of SpectaQL is to help you keep your documentation complete, > current and beautiful with the least amount of pain as possible. > > Out of the box, SpectaQL delivers a 3-column page with a modern look > and feel. However, many aspects can be customized with ease, and just > about everything can be customized if you're willing to dig in.

Solution 6 - Graphql

If you're a Sphinx / ReadTheDocs User, you may find https://github.com/hasura/sphinx-graphiql useful.

Solution 7 - Graphql

I've been actively working on a new solution for this for the past few months, because the existing solutions were not fitting my needs. They were not easy to customise or simply not maintained at all.

https://github.com/magidoc-org/magidoc

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionFrancisco CanelaView Question on Stackoverflow
Solution 1 - GraphqljunView Answer on Stackoverflow
Solution 2 - GraphqlhelferView Answer on Stackoverflow
Solution 3 - GraphqlZdeněk DušátkoView Answer on Stackoverflow
Solution 4 - GraphqlLeOn - Han LiView Answer on Stackoverflow
Solution 5 - GraphqlpylippView Answer on Stackoverflow
Solution 6 - GraphqlAlastair McCormackView Answer on Stackoverflow
Solution 7 - GraphqlSunny PelletierView Answer on Stackoverflow