[Modern] Error with .json schema

[adjourn]

Docs:

The relay-compiler script requires both the directory which holds your source files as well as a path to your GraphQL schema in either a .json or .graphql schema file.

Log:

> relay-compiler --src ./js --schema ./schema.json

HINT: pass --watch to keep watching for changes.
Parsed default in 0.04s

Writing default
Error: Error loading schema. Expected the schema to be a .graphql file using the
GraphQL schema definition language.

JSON file:

{
  "queryType": {
    "name": "Query"
  },
  "mutationType": {
    "name": "Mutation"
  },
  "subscriptionType": null,
  "types": [
    {
      "kind": "OBJECT",
      "name": "Query",
      "description": null,
      "fields": [

  // etc

[sibelius]

you should use schema.graphql instead of schema.json

[adjourn]

@sibelius
Im trying to find a way to convert it to .graphql (I get that particular schema from GraphQL endpoint) but nethertheless, the main question to authors is if .json an upcoming feature or are docs misleading?

[sibelius]

use this script: https://github.com/entria/graphql-dataloader-boilerplate/blob/master/scripts/updateSchema.js#L40

[sibelius]

.json is used on Relay Classic

.graphql is used on Relay Modern

[leethree]

@unirey you can parse schema.json using buildClientSchema from graphql/utilities, and then print it using printSchema.

[sibelius]

@leethree could you provide a code example of it?

[leethree]

This should work:

import fs from 'fs';
import {
  buildClientSchema,
  printSchema,
} from 'graphql/utilities';

const schema = buildClientSchema(require('schema.json').data);
fs.writeFileSync(
  `schema.graphql`,
  printSchema(schema),
);

[kassens]

@leebyron: What's your intuition, should we just support .json everywhere in addition to .graphql?

[joho]

FWIW I'd appreciate if both formats were supported.

I'm working with a graphql endpoint that currently only spits out the json form of the schema. I (now) understand there are workarounds, but I'm working on a react app that's currently ejected from create-react-app but I'd love to have a path back towards un-ejecting when facebook/create-react-app#462 arrives, which gets less and less likely as I add extra build steps into the process.

[leebyron]

It's easy for us to support both, so we should @kassens

[leebyron]

Fwiw the Babel plugin supports both. This just seems like a small oversight in the compiler