Allow legacy names in client schemas.

Author: alloy

src/utilities/__tests__/buildClientSchema-test.js

@@ -669,6 +669,34 @@ describe('Type System: build schema from introspection', () => {
     expect(secondIntrospection.data).to.containSubset(newIntrospection);
   });
 
+  it('builds a schema with legacy names', () => {
+    const introspection = {
+      __schema: {
+        queryType: {
+          name: 'Query',
+        },
+        types: [
+          {
+            name: 'Query',
+            kind: 'OBJECT',
+            fields: [
+              {
+                name: '__badName',
+                args: [],
+                type: { name: 'String' },
+              },
+            ],
+            interfaces: [],
+          },
+        ],
+      },
+    };
+    const schema = buildClientSchema(introspection, {
+      allowedLegacyNames: ['__badName'],
+    });
+    expect(schema.__allowedLegacyNames).to.deep.equal(['__badName']);
+  });
+
   it('builds a schema aware of deprecation', async () => {
     const schema = new GraphQLSchema({
       query: new GraphQLObjectType({

src/utilities/buildClientSchema.js

@@ -60,15 +60,10 @@ import type {
   IntrospectionNamedTypeRef,
 } from './introspectionQuery';
 
+import type { GraphQLSchemaValidationOptions } from '../type/schema';
+
 type Options = {|
-  /**
-   * When building a schema from a GraphQL service's introspection result, it
-   * might be safe to assume the schema is valid. Set to true to assume the
-   * produced schema is valid.
-   *
-   * Default: false
-   */
-  assumeValid?: boolean,
+  ...GraphQLSchemaValidationOptions,
 |};
 
 /**
@@ -414,5 +409,6 @@ export function buildClientSchema(
     types,
     directives,
     assumeValid: options && options.assumeValid,
+    allowedLegacyNames: options && options.allowedLegacyNames,
   });
 }