From 093c990c56f919e3e06f71baec42dbd159573d5b Mon Sep 17 00:00:00 2001 From: Rhys Evans Date: Fri, 29 Nov 2024 12:20:49 +0000 Subject: [PATCH] docs: document that fetch can be passed into expectations in jest wrapper --- docs/docs/wrappers/index.md | 3 +++ docs/docs/wrappers/jest.md | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/docs/wrappers/index.md b/docs/docs/wrappers/index.md index 96e06bce..207086a0 100644 --- a/docs/docs/wrappers/index.md +++ b/docs/docs/wrappers/index.md @@ -2,3 +2,6 @@ sidebar_label: Wrappers sidebar_position: 8 --- + +- [@fetch-mock/jest](/fetch-mock/docs/wrappers/jest) +- [@fetch-mock/vitest](/fetch-mock/docs/wrappers/vitest) diff --git a/docs/docs/wrappers/jest.md b/docs/docs/wrappers/jest.md index 346b9e71..292548d2 100644 --- a/docs/docs/wrappers/jest.md +++ b/docs/docs/wrappers/jest.md @@ -70,7 +70,7 @@ Note that these **will not** clear any sticky routes added to fetchMock. You wil ### Expect extensions -These are added to jest automatically and are available on any expect call that is passed fetchMock as an argument. Their behaviour is similar to the jest expectation methods mentioned in the comments below +These are added to jest automatically and are available on any expect call that is passed `fetchMock` (or `fetch`, if it has been mocked globally by fetchMock) as an argument. Their behaviour is similar to the jest expectation methods mentioned in the comments below ```js expect(fetchMock).toHaveFetched(filter, options); // .toHaveBeenCalled()/.toHaveBeenCalledWith()