Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix typo/punctuation in MockFunctionAPI.md #12887

Merged
merged 3 commits into from Jun 3, 2022
Merged

fix typo/punctuation in MockFunctionAPI.md #12887

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d3cdf1a
fix typo/punctuation in MockFunctionAPI.md
ChrisCoastal May 30, 2022
38e3a82
fix typo/punctuation in docs/MockFunctionAPI.md
ChrisCoastal May 30, 2022
50657b0
fix typo/punctuation in v28.0/MockFunctionAPI.md
ChrisCoastal May 30, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/MockFunctionAPI.md
View file
Open in desktop
Expand Up @@ -586,7 +586,7 @@ Please consult the [Getting Started](GettingStarted.md#using-typescript) guide f

### `jest.fn(implementation?)`

Correct mock typings will be inferred, if implementation is passed to [`jest.fn()`](JestObjectAPI.md#jestfnimplementation). There are many use cases there the implementation is omitted. To ensure type safety you may pass a generic type argument (also see the examples above for more reference):
Correct mock typings will be inferred if implementation is passed to [`jest.fn()`](JestObjectAPI.md#jestfnimplementation). There are many use cases where the implementation is omitted. To ensure type safety you may pass a generic type argument (also see the examples above for more reference):

```ts
import {expect, jest, test} from '@jest/globals';
Expand Down
2 changes: 1 addition & 1 deletion website/versioned_docs/version-28.0/MockFunctionAPI.md
View file
Open in desktop
Expand Up @@ -586,7 +586,7 @@ Please consult the [Getting Started](GettingStarted.md#using-typescript) guide f

### `jest.fn(implementation?)`

Correct mock typings will be inferred, if implementation is passed to [`jest.fn()`](JestObjectAPI.md#jestfnimplementation). There are many use cases there the implementation is omitted. To ensure type safety you may pass a generic type argument (also see the examples above for more reference):
Correct mock typings will be inferred if implementation is passed to [`jest.fn()`](JestObjectAPI.md#jestfnimplementation). There are many use cases where the implementation is omitted. To ensure type safety you may pass a generic type argument (also see the examples above for more reference):

```ts
import {expect, jest, test} from '@jest/globals';
Expand Down
2 changes: 1 addition & 1 deletion website/versioned_docs/version-28.1/MockFunctionAPI.md
View file
Open in desktop
Expand Up @@ -586,7 +586,7 @@ Please consult the [Getting Started](GettingStarted.md#using-typescript) guide f

### `jest.fn(implementation?)`

Correct mock typings will be inferred, if implementation is passed to [`jest.fn()`](JestObjectAPI.md#jestfnimplementation). There are many use cases there the implementation is omitted. To ensure type safety you may pass a generic type argument (also see the examples above for more reference):
Correct mock typings will be inferred if implementation is passed to [`jest.fn()`](JestObjectAPI.md#jestfnimplementation). There are many use cases where the implementation is omitted. To ensure type safety you may pass a generic type argument (also see the examples above for more reference):

```ts
import {expect, jest, test} from '@jest/globals';
Expand Down