[deploy_website] Spelling (#2598)

* spelling: access Signed-off-by: Josh Soref <[email protected]> * spelling: additional Signed-off-by: Josh Soref <[email protected]> * spelling: additionally Signed-off-by: Josh Soref <[email protected]> * spelling: alexandre Signed-off-by: Josh Soref <[email protected]> * spelling: anyway Signed-off-by: Josh Soref <[email protected]> * spelling: applying Signed-off-by: Josh Soref <[email protected]> * spelling: arbitrary Signed-off-by: Josh Soref <[email protected]> * spelling: argument Signed-off-by: Josh Soref <[email protected]> * spelling: because Signed-off-by: Josh Soref <[email protected]> * spelling: behavior Signed-off-by: Josh Soref <[email protected]> * spelling: caeser Signed-off-by: Josh Soref <[email protected]> * spelling: compatibility Signed-off-by: Josh Soref <[email protected]> * spelling: consistent Signed-off-by: Josh Soref <[email protected]> * spelling: containing Signed-off-by: Josh Soref <[email protected]> * spelling: conversion Signed-off-by: Josh Soref <[email protected]> * spelling: couldn't Signed-off-by: Josh Soref <[email protected]> * spelling: crashes Signed-off-by: Josh Soref <[email protected]> * spelling: default Signed-off-by: Josh Soref <[email protected]> * spelling: description Signed-off-by: Josh Soref <[email protected]> * spelling: determine Signed-off-by: Josh Soref <[email protected]> * spelling: doesn't Signed-off-by: Josh Soref <[email protected]> * spelling: don't Signed-off-by: Josh Soref <[email protected]> * spelling: easier Signed-off-by: Josh Soref <[email protected]> * spelling: errors Signed-off-by: Josh Soref <[email protected]> * spelling: executable Signed-off-by: Josh Soref <[email protected]> * spelling: extensions Signed-off-by: Josh Soref <[email protected]> * spelling: fragment Signed-off-by: Josh Soref <[email protected]> * spelling: github Signed-off-by: Josh Soref <[email protected]> * spelling: guarantee Signed-off-by: Josh Soref <[email protected]> * spelling: handy Signed-off-by: Josh Soref <[email protected]> * spelling: ignore Signed-off-by: Josh Soref <[email protected]> * spelling: ignored Signed-off-by: Josh Soref <[email protected]> * spelling: implementers Signed-off-by: Josh Soref <[email protected]> * spelling: important Signed-off-by: Josh Soref <[email protected]> * spelling: indentation Signed-off-by: Josh Soref <[email protected]> * spelling: interface Signed-off-by: Josh Soref <[email protected]> * spelling: internal Signed-off-by: Josh Soref <[email protected]> * spelling: javascript Signed-off-by: Josh Soref <[email protected]> * spelling: mocks Signed-off-by: Josh Soref <[email protected]> * spelling: modifiable Signed-off-by: Josh Soref <[email protected]> * spelling: modify Signed-off-by: Josh Soref <[email protected]> * spelling: necessarily Signed-off-by: Josh Soref <[email protected]> * spelling: object Signed-off-by: Josh Soref <[email protected]> * spelling: observable Signed-off-by: Josh Soref <[email protected]> * spelling: optional Signed-off-by: Josh Soref <[email protected]> * spelling: optionally Signed-off-by: Josh Soref <[email protected]> * spelling: overridden Signed-off-by: Josh Soref <[email protected]> * spelling: override Signed-off-by: Josh Soref <[email protected]> * spelling: parenthetically Signed-off-by: Josh Soref <[email protected]> * spelling: particularly Signed-off-by: Josh Soref <[email protected]> * spelling: receive Signed-off-by: Josh Soref <[email protected]> * spelling: retrieve Signed-off-by: Josh Soref <[email protected]> * spelling: return Signed-off-by: Josh Soref <[email protected]> * spelling: schema Signed-off-by: Josh Soref <[email protected]> * spelling: separately Signed-off-by: Josh Soref <[email protected]> * spelling: specifying Signed-off-by: Josh Soref <[email protected]> * spelling: split Signed-off-by: Josh Soref <[email protected]> * spelling: subscription Signed-off-by: Josh Soref <[email protected]> * spelling: toolkit Signed-off-by: Josh Soref <[email protected]> * spelling: transform Signed-off-by: Josh Soref <[email protected]> * spelling: valid Signed-off-by: Josh Soref <[email protected]>
ardatan · Feb 16, 2021 · 42d72ad · 42d72ad
1 parent 856c520
commit 42d72ad
Show file tree

Hide file tree

Showing 66 changed files with 119 additions and 119 deletions.
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-[![toolskit](https://user-images.githubusercontent.com/20847995/80261023-feb6e380-8691-11ea-8680-5747fa02c5d8.gif)](https://graphql-tools.com)
+[![toolkit](https://user-images.githubusercontent.com/20847995/80261023-feb6e380-8691-11ea-8680-5747fa02c5d8.gif)](https://graphql-tools.com)
 
 [![npm version](https://badge.fury.io/js/%40graphql-tools%2Futils.svg)](https://badge.fury.io/js/%40graphql-tools%2Futils)
 [![CI](https://github.com/ardatan/graphql-tools/workflows/CI/badge.svg)](https://github.com/ardatan/graphql-tools/actions)
@@ -23,7 +23,7 @@ This package provides a few useful ways to create a GraphQL schema:
 
 If you want to bind your JavaScript GraphQL schema to an HTTP server, you can use [`express-graphql`](https://github.com/graphql/express-graphql).
 
-You can develop your Javascript based GraphQL API with `graphql-tools` and `express-graphql` together: One to write the schema and resolver code, and the other to connect it to a web server.
+You can develop your JavaScript based GraphQL API with `graphql-tools` and `express-graphql` together: One to write the schema and resolver code, and the other to connect it to a web server.
 
 ## Example
 

diff --git a/packages/batch-delegate/CHANGELOG.md b/packages/batch-delegate/CHANGELOG.md
@@ -23,7 +23,7 @@
 
   * The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
 
-  * The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executabel) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
+  * The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executable) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
 
   * `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
 

diff --git a/packages/batch-execute/CHANGELOG.md b/packages/batch-execute/CHANGELOG.md
@@ -19,7 +19,7 @@
 
   - The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
 
-  - The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executabel) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
+  - The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executable) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
 
   - `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
 

diff --git a/packages/delegate/CHANGELOG.md b/packages/delegate/CHANGELOG.md
@@ -121,7 +121,7 @@
 
   - The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
 
-  - The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executabel) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
+  - The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executable) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
 
   - `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
 

diff --git a/packages/delegate/src/defaultMergedResolver.ts b/packages/delegate/src/defaultMergedResolver.ts
@@ -10,7 +10,7 @@ import { ExternalObject } from './types';
  * Resolver that knows how to:
  * a) handle aliases for proxied schemas
  * b) handle errors from proxied schemas
- * c) handle external to internal enum coversion
+ * c) handle external to internal enum conversion
  */
 export function defaultMergedResolver(
   parent: ExternalObject,

diff --git a/packages/graphql-tag-pluck/CHANGELOG.md b/packages/graphql-tag-pluck/CHANGELOG.md
@@ -41,8 +41,8 @@
 
 ### Patch Changes
 
-- e9ed9394: Change intenral API to add more details on found locations, and export parseCode for lower-level parsing
-- 54b440a9: allow to skip identation while plucking
+- e9ed9394: Change internal API to add more details on found locations, and export parseCode for lower-level parsing
+- 54b440a9: allow to skip indentation while plucking
 
 ## 6.2.4
 

diff --git a/packages/graphql-tag-pluck/src/visitor.ts b/packages/graphql-tag-pluck/src/visitor.ts
@@ -181,7 +181,7 @@ export default (code: string, out: any, options: GraphQLTagPluckOptions = {}) =>
         // Slice quotes
         .slice(start + 1, end - 1)
         // Erase string interpolations as we gonna export everything as a single
-        // string anyways
+        // string anyway
         .replace(/\$\{[^}]*\}/g, '')
         .split('\\`')
         .join('`'),

diff --git a/packages/graphql-tools/CHANGELOG.md b/packages/graphql-tools/CHANGELOG.md
@@ -48,7 +48,7 @@
 
   * The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
 
-  * The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executabel) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
+  * The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executable) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
 
   * `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
 

diff --git a/packages/import/tests/schema/import-schema.spec.ts b/packages/import/tests/schema/import-schema.spec.ts
@@ -95,7 +95,7 @@ describe('importSchema', () => {
   });
 
   test('parseSDL: non-import comment', () => {
-    expect(parseSDL(`#importent: comment`)).toEqual([]);
+    expect(parseSDL(`#important: comment`)).toEqual([]);
   });
 
   test('parse: multi line import', () => {

diff --git a/packages/links/CHANGELOG.md b/packages/links/CHANGELOG.md
@@ -67,7 +67,7 @@
 
   - The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
 
-  - The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executabel) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
+  - The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executable) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
 
   - `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
 

diff --git a/packages/load-files/tests/file-scanner.spec.ts b/packages/load-files/tests/file-scanner.spec.ts
@@ -205,7 +205,7 @@ describe('file scanner', function() {
           },
         },
       ],
-      note: 'ingore index files',
+      note: 'ignore index files',
       extensions: ['js'],
       compareValue: true,
       ignoreIndex: true,

diff --git a/packages/load-files/tests/test-assets/12/index.ts b/packages/load-files/tests/test-assets/12/index.ts
@@ -1,5 +1,5 @@
 export default {
-  IngoredType: {
+  IgnoredType: {
     f: '12',
   },
 };
diff --git a/packages/load/tests/loaders/schema/schema-from-typedefs.spec.ts b/packages/load/tests/loaders/schema/schema-from-typedefs.spec.ts
@@ -51,7 +51,7 @@ describe('schema from typedefs', () => {
       }
     });
 
-    it('should ignore graphql documents when loading a scehma', async () => {
+    it('should ignore graphql documents when loading a schema', async () => {
       const glob = './tests/loaders/schema/test-files/schema-dir/*.non-schema.graphql';
 
       try {

diff --git a/packages/loaders/code-file/tests/load-from-code-file.spec.ts b/packages/loaders/code-file/tests/load-from-code-file.spec.ts
@@ -22,7 +22,7 @@ describe('loadFromCodeFile', () => {
     }
   });
 
-  it('should load a vaild file', async () => {
+  it('should load a valid file', async () => {
     const loaded = await loader.load('./test-files/valid-doc.js', {
       noRequire: true,
       fs,
@@ -85,7 +85,7 @@ describe('loadFromCodeFileSync', () => {
     }).toThrowError('Syntax Error: Unexpected Name "InvalidGetUser"')
   });
 
-  it('should load a vaild file', () => {
+  it('should load a valid file', () => {
     const loaded = loader.loadSync('./test-files/valid-doc.js', {
       noRequire: true,
       fs,

diff --git a/packages/loaders/git/tests/test-files/introspection.json b/packages/loaders/git/tests/test-files/introspection.json
@@ -963,15 +963,15 @@
       },
       {
         "name": "specifiedBy",
-        "description": "Exposes a URL that specifies the behaviour of this scalar.",
+        "description": "Exposes a URL that specifies the behavior of this scalar.",
         "isRepeatable": false,
         "locations": [
           "SCALAR"
         ],
         "args": [
           {
             "name": "url",
-            "description": "The URL that specifies the behaviour of this scalar.",
+            "description": "The URL that specifies the behavior of this scalar.",
             "type": {
               "kind": "NON_NULL",
               "name": null,

diff --git a/packages/loaders/github/tests/schema-from-github.spec.ts b/packages/loaders/github/tests/schema-from-github.spec.ts
@@ -27,7 +27,7 @@ function normalize(doc: string): string {
     return print(parse(doc));
 }
 
-test('load schema from Github', async () => {
+test('load schema from GitHub', async () => {
   let headers: Record<string, string> = {};
   let query: string;
   let variables: any;

diff --git a/packages/loaders/json-file/tests/test-files/introspection.json b/packages/loaders/json-file/tests/test-files/introspection.json
@@ -963,15 +963,15 @@
       },
       {
         "name": "specifiedBy",
-        "description": "Exposes a URL that specifies the behaviour of this scalar.",
+        "description": "Exposes a URL that specifies the behavior of this scalar.",
         "isRepeatable": false,
         "locations": [
           "SCALAR"
         ],
         "args": [
           {
             "name": "url",
-            "description": "The URL that specifies the behaviour of this scalar.",
+            "description": "The URL that specifies the behavior of this scalar.",
             "type": {
               "kind": "NON_NULL",
               "name": null,

diff --git a/packages/loaders/prisma/src/prisma-yml/PrismaDefinition.test.ts b/packages/loaders/prisma/src/prisma-yml/PrismaDefinition.test.ts
@@ -177,7 +177,7 @@ type User @model {
   /**
    * This test ensures, that GRAPHCOOL_SECRET can't be injected anymore
    */
-  test('dont load yml with secret and env var in args', async () => {
+  test(`don't load yml with secret and env var in args`, async () => {
     const yml = `\
 service: jj
 stage: dev

diff --git a/packages/loaders/prisma/src/prisma-yml/__snapshots__/PrismaDefinition.test.ts.snap b/packages/loaders/prisma/src/prisma-yml/__snapshots__/PrismaDefinition.test.ts.snap
@@ -157,7 +157,7 @@ Array [
 ]
 `;
 
-exports[`prisma definition dont load yml with secret and env var in args 1`] = `
+exports[`prisma definition don't load yml with secret and env var in args 1`] = `
 [Error: Invalid prisma.yml file
 prisma.yml should NOT have additional properties. additionalProperty: service]
 `;

diff --git a/packages/loaders/prisma/src/prisma-yml/utils/parseEndpoint.test.ts b/packages/loaders/prisma/src/prisma-yml/utils/parseEndpoint.test.ts
@@ -9,7 +9,7 @@ describe('parseEndpoint', () => {
   });
   test('local behind a proxy', () => {
     // This snapshot will be incorrect for now as URL does not have enough
-    // information to detemine if something is truly local
+    // information to determine if something is truly local
     expect(parseEndpoint('http://local.dev')).toMatchSnapshot();
   });
   test('work for url with service', () => {

diff --git a/packages/merge/CHANGELOG.md b/packages/merge/CHANGELOG.md
@@ -33,7 +33,7 @@
 
   - The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
 
-  - The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executabel) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
+  - The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executable) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
 
   - `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
 

diff --git a/packages/mock/CHANGELOG.md b/packages/mock/CHANGELOG.md
@@ -32,7 +32,7 @@
 
   - The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
 
-  - The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executabel) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
+  - The `transformSchema` method may wish to create additional delegating resolvers and so it is now provided the `subschemaConfig` and final (non-executable) `transformedSchema` parameters. As in v6, the `transformSchema` is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executable) initial result. In v7, the individual `transformSchema` methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.
 
   - `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
 

diff --git a/packages/mock/src/MockStore.ts b/packages/mock/src/MockStore.ts
@@ -77,7 +77,7 @@ export class MockStore implements IMockStore {
     if (typeof _typeName !== 'string') {
       if (_key === undefined) {
         if (isRef<KeyT>(_typeName)) {
-          throw new Error("Can't provide a ref as first arguement and no other argument");
+          throw new Error("Can't provide a ref as first argument and no other argument");
         }
         // get({...})
         return this.getImpl(_typeName);
@@ -139,7 +139,7 @@ export class MockStore implements IMockStore {
     if (typeof _typeName !== 'string') {
       if (_key === undefined) {
         if (isRef<KeyT>(_typeName)) {
-          throw new Error("Can't provide a ref as first arguement and no other argument");
+          throw new Error("Can't provide a ref as first argument and no other argument");
         }
         // set({...})
         return this.setImpl(_typeName);
@@ -260,7 +260,7 @@ export class MockStore implements IMockStore {
       this.store[typeName][key] = {};
     }
 
-    // if already set and we don't ovveride
+    // if already set and we don't override
     if (this.store[typeName][key][fieldNameInStore] !== undefined && noOverride) {
       return;
     }
@@ -292,7 +292,7 @@ export class MockStore implements IMockStore {
     const fieldTypeName = fieldType.toString();
     if (value === null) {
       if (!isNullableType(fieldType)) {
-        throw new Error(`should not be null bacause ${fieldTypeName} is not nullable. Received null.`);
+        throw new Error(`should not be null because ${fieldTypeName} is not nullable. Received null.`);
       }
     }
 
@@ -420,7 +420,7 @@ export class MockStore implements IMockStore {
     if (value !== undefined) return value;
 
     const type = this.getType(typeName);
-    // GraphQL 14 Compability
+    // GraphQL 14 Compatibility
     const interfaces = 'getInterfaces' in type ? type.getInterfaces() : [];
 
     if (interfaces.length > 0) {

diff --git a/packages/mock/src/addMocksToSchema.ts b/packages/mock/src/addMocksToSchema.ts
@@ -134,7 +134,7 @@ export function addMocksToSchema({
       });
     }
 
-    // we have to handle the root mutation, root query and root subscripton types
+    // we have to handle the root mutation, root query and root subscription types
     // differently, because no resolver is called at the root
     if (isRootType(info.parentType, info.schema)) {
       return store.get({

diff --git a/packages/mock/src/index.ts b/packages/mock/src/index.ts
@@ -36,7 +36,7 @@ export * from './MockList';
  */
 export function createMockStore(options: {
   /**
-   * The `schema` to based mokcks on.
+   * The `schema` to based mocks on.
    */
   schema: GraphQLSchema;