Skip to content

Commit 42d72ad

Browse files
jsorefjsoref
authored
[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]>
1 parent 856c520 commit 42d72ad

File tree

66 files changed

+119
-119
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

66 files changed

+119
-119
lines changed

‎README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
[![toolskit](https://user-images.githubusercontent.com/20847995/80261023-feb6e380-8691-11ea-8680-5747fa02c5d8.gif)](https://graphql-tools.com)
1+
[![toolkit](https://user-images.githubusercontent.com/20847995/80261023-feb6e380-8691-11ea-8680-5747fa02c5d8.gif)](https://graphql-tools.com)
22

33
[![npm version](https://badge.fury.io/js/%40graphql-tools%2Futils.svg)](https://badge.fury.io/js/%40graphql-tools%2Futils)
44
[![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:
2323

2424
If you want to bind your JavaScript GraphQL schema to an HTTP server, you can use [`express-graphql`](https://github.com/graphql/express-graphql).
2525

26-
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.
26+
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.
2727

2828
## Example
2929

‎packages/batch-delegate/CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@
2323

2424
* The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
2525

26-
* 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.
26+
* 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.
2727

2828
* `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
2929

‎packages/batch-execute/CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@
1919

2020
- The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
2121

22-
- 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.
22+
- 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.
2323

2424
- `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
2525

‎packages/delegate/CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@
121121

122122
- The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
123123

124-
- 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.
124+
- 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.
125125

126126
- `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
127127

‎packages/delegate/src/defaultMergedResolver.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ import { ExternalObject } from './types';
1010
* Resolver that knows how to:
1111
* a) handle aliases for proxied schemas
1212
* b) handle errors from proxied schemas
13-
* c) handle external to internal enum coversion
13+
* c) handle external to internal enum conversion
1414
*/
1515
export function defaultMergedResolver(
1616
parent: ExternalObject,

‎packages/graphql-tag-pluck/CHANGELOG.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,8 +41,8 @@
4141

4242
### Patch Changes
4343

44-
- e9ed9394: Change intenral API to add more details on found locations, and export parseCode for lower-level parsing
45-
- 54b440a9: allow to skip identation while plucking
44+
- e9ed9394: Change internal API to add more details on found locations, and export parseCode for lower-level parsing
45+
- 54b440a9: allow to skip indentation while plucking
4646

4747
## 6.2.4
4848

‎packages/graphql-tag-pluck/src/visitor.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,7 @@ export default (code: string, out: any, options: GraphQLTagPluckOptions = {}) =>
181181
// Slice quotes
182182
.slice(start + 1, end - 1)
183183
// Erase string interpolations as we gonna export everything as a single
184-
// string anyways
184+
// string anyway
185185
.replace(/\$\{[^}]*\}/g, '')
186186
.split('\\`')
187187
.join('`'),

‎packages/graphql-tools/CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@
4848

4949
* The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
5050

51-
* 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.
51+
* 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.
5252

5353
* `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
5454

‎packages/import/tests/schema/import-schema.spec.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ describe('importSchema', () => {
9595
});
9696

9797
test('parseSDL: non-import comment', () => {
98-
expect(parseSDL(`#importent: comment`)).toEqual([]);
98+
expect(parseSDL(`#important: comment`)).toEqual([]);
9999
});
100100

101101
test('parse: multi line import', () => {

‎packages/links/CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@
6767

6868
- The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
6969

70-
- 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.
70+
- 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.
7171

7272
- `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
7373

‎packages/load-files/tests/file-scanner.spec.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@ describe('file scanner', function() {
205205
},
206206
},
207207
],
208-
note: 'ingore index files',
208+
note: 'ignore index files',
209209
extensions: ['js'],
210210
compareValue: true,
211211
ignoreIndex: true,

‎packages/load-files/tests/test-assets/12/index.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
export default {
2-
IngoredType: {
2+
IgnoredType: {
33
f: '12',
44
},
55
};

‎packages/load/tests/loaders/schema/schema-from-typedefs.spec.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ describe('schema from typedefs', () => {
5151
}
5252
});
5353

54-
it('should ignore graphql documents when loading a scehma', async () => {
54+
it('should ignore graphql documents when loading a schema', async () => {
5555
const glob = './tests/loaders/schema/test-files/schema-dir/*.non-schema.graphql';
5656

5757
try {

‎packages/loaders/code-file/tests/load-from-code-file.spec.ts

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ describe('loadFromCodeFile', () => {
2222
}
2323
});
2424

25-
it('should load a vaild file', async () => {
25+
it('should load a valid file', async () => {
2626
const loaded = await loader.load('./test-files/valid-doc.js', {
2727
noRequire: true,
2828
fs,
@@ -85,7 +85,7 @@ describe('loadFromCodeFileSync', () => {
8585
}).toThrowError('Syntax Error: Unexpected Name "InvalidGetUser"')
8686
});
8787

88-
it('should load a vaild file', () => {
88+
it('should load a valid file', () => {
8989
const loaded = loader.loadSync('./test-files/valid-doc.js', {
9090
noRequire: true,
9191
fs,

‎packages/loaders/git/tests/test-files/introspection.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -963,15 +963,15 @@
963963
},
964964
{
965965
"name": "specifiedBy",
966-
"description": "Exposes a URL that specifies the behaviour of this scalar.",
966+
"description": "Exposes a URL that specifies the behavior of this scalar.",
967967
"isRepeatable": false,
968968
"locations": [
969969
"SCALAR"
970970
],
971971
"args": [
972972
{
973973
"name": "url",
974-
"description": "The URL that specifies the behaviour of this scalar.",
974+
"description": "The URL that specifies the behavior of this scalar.",
975975
"type": {
976976
"kind": "NON_NULL",
977977
"name": null,

‎packages/loaders/github/tests/schema-from-github.spec.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ function normalize(doc: string): string {
2727
return print(parse(doc));
2828
}
2929

30-
test('load schema from Github', async () => {
30+
test('load schema from GitHub', async () => {
3131
let headers: Record<string, string> = {};
3232
let query: string;
3333
let variables: any;

‎packages/loaders/json-file/tests/test-files/introspection.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -963,15 +963,15 @@
963963
},
964964
{
965965
"name": "specifiedBy",
966-
"description": "Exposes a URL that specifies the behaviour of this scalar.",
966+
"description": "Exposes a URL that specifies the behavior of this scalar.",
967967
"isRepeatable": false,
968968
"locations": [
969969
"SCALAR"
970970
],
971971
"args": [
972972
{
973973
"name": "url",
974-
"description": "The URL that specifies the behaviour of this scalar.",
974+
"description": "The URL that specifies the behavior of this scalar.",
975975
"type": {
976976
"kind": "NON_NULL",
977977
"name": null,

‎packages/loaders/prisma/src/prisma-yml/PrismaDefinition.test.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ type User @model {
177177
/**
178178
* This test ensures, that GRAPHCOOL_SECRET can't be injected anymore
179179
*/
180-
test('dont load yml with secret and env var in args', async () => {
180+
test(`don't load yml with secret and env var in args`, async () => {
181181
const yml = `\
182182
service: jj
183183
stage: dev

‎packages/loaders/prisma/src/prisma-yml/__snapshots__/PrismaDefinition.test.ts.snap

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ Array [
157157
]
158158
`;
159159

160-
exports[`prisma definition dont load yml with secret and env var in args 1`] = `
160+
exports[`prisma definition don't load yml with secret and env var in args 1`] = `
161161
[Error: Invalid prisma.yml file
162162
prisma.yml should NOT have additional properties. additionalProperty: service]
163163
`;

‎packages/loaders/prisma/src/prisma-yml/utils/parseEndpoint.test.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ describe('parseEndpoint', () => {
99
});
1010
test('local behind a proxy', () => {
1111
// This snapshot will be incorrect for now as URL does not have enough
12-
// information to detemine if something is truly local
12+
// information to determine if something is truly local
1313
expect(parseEndpoint('http://local.dev')).toMatchSnapshot();
1414
});
1515
test('work for url with service', () => {

‎packages/merge/CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333

3434
- The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
3535

36-
- 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.
36+
- 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.
3737

3838
- `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
3939

‎packages/mock/CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@
3232

3333
- The `transformRequest`/`transformResult` methods are now provided additional `delegationContext` and `transformationContext` arguments -- these were introduced in v6, but previously optional.
3434

35-
- 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.
35+
- 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.
3636

3737
- `applySchemaTransforms` parameters have been updated to match and support the `transformSchema` parameters above.
3838

‎packages/mock/src/MockStore.ts

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ export class MockStore implements IMockStore {
7777
if (typeof _typeName !== 'string') {
7878
if (_key === undefined) {
7979
if (isRef<KeyT>(_typeName)) {
80-
throw new Error("Can't provide a ref as first arguement and no other argument");
80+
throw new Error("Can't provide a ref as first argument and no other argument");
8181
}
8282
// get({...})
8383
return this.getImpl(_typeName);
@@ -139,7 +139,7 @@ export class MockStore implements IMockStore {
139139
if (typeof _typeName !== 'string') {
140140
if (_key === undefined) {
141141
if (isRef<KeyT>(_typeName)) {
142-
throw new Error("Can't provide a ref as first arguement and no other argument");
142+
throw new Error("Can't provide a ref as first argument and no other argument");
143143
}
144144
// set({...})
145145
return this.setImpl(_typeName);
@@ -260,7 +260,7 @@ export class MockStore implements IMockStore {
260260
this.store[typeName][key] = {};
261261
}
262262

263-
// if already set and we don't ovveride
263+
// if already set and we don't override
264264
if (this.store[typeName][key][fieldNameInStore] !== undefined && noOverride) {
265265
return;
266266
}
@@ -292,7 +292,7 @@ export class MockStore implements IMockStore {
292292
const fieldTypeName = fieldType.toString();
293293
if (value === null) {
294294
if (!isNullableType(fieldType)) {
295-
throw new Error(`should not be null bacause ${fieldTypeName} is not nullable. Received null.`);
295+
throw new Error(`should not be null because ${fieldTypeName} is not nullable. Received null.`);
296296
}
297297
}
298298

@@ -420,7 +420,7 @@ export class MockStore implements IMockStore {
420420
if (value !== undefined) return value;
421421

422422
const type = this.getType(typeName);
423-
// GraphQL 14 Compability
423+
// GraphQL 14 Compatibility
424424
const interfaces = 'getInterfaces' in type ? type.getInterfaces() : [];
425425

426426
if (interfaces.length > 0) {

‎packages/mock/src/addMocksToSchema.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ export function addMocksToSchema({
134134
});
135135
}
136136

137-
// we have to handle the root mutation, root query and root subscripton types
137+
// we have to handle the root mutation, root query and root subscription types
138138
// differently, because no resolver is called at the root
139139
if (isRootType(info.parentType, info.schema)) {
140140
return store.get({

‎packages/mock/src/index.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ export * from './MockList';
3636
*/
3737
export function createMockStore(options: {
3838
/**
39-
* The `schema` to based mokcks on.
39+
* The `schema` to based mocks on.
4040
*/
4141
schema: GraphQLSchema;
4242

0 commit comments

Comments
 (0)