Support configuring via typeDefinitions

See example here

https://github.com/tonyxiao/eslint-plugin-graphql/blob/master/test/updateSchemaJson.js#L5-L11

Basically allow people to import a package which represents their server and generate a schema based on their server code. Could be either the result of graphql.buildASTSchema, a string which contains graphQL schema type definitions, or path to a .graphql file.

[tonyxiao]

Oh wait, that’s just what you were talking about earlier…

https://github.com/graphcool/graphql-config/blob/master/README.md#use-local-schema-file-graphqljs

I guess I totally misread for some reason. Closing issue then. 😃

[tonyxiao]

The advantage of configuring via an actual schema / type definitions is that you don’t need a running server somewhere and you can make sure the test you are running is always testing against the version of schema that you wrote the code for (So going back to an old commit, test wont be magically broken because API server has changed).

I imagine you have to provide an import path for us to find the module which contains the AST schema. So maybe an additional option like so?

.graphqlrc

{
  "schema": "yourpackage/schema"
}

yourpackage/schema.js

import graphql from 'graphql'

const typeDefinition = `
...
`
export default graphql.buildASTSchema(graphql.parse(typeDefinition));