From ffe60d8aa45b12306cb4ae4db78845b3aae5d19e Mon Sep 17 00:00:00 2001 From: Rhys Evans Date: Sun, 21 Jul 2024 14:11:47 +0100 Subject: [PATCH] docs: document widespread use of CallLog --- docs/blog/2024-07-21-introducing-core.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/blog/2024-07-21-introducing-core.md b/docs/blog/2024-07-21-introducing-core.md index f385dea4..f450b80f 100644 --- a/docs/blog/2024-07-21-introducing-core.md +++ b/docs/blog/2024-07-21-introducing-core.md @@ -83,7 +83,7 @@ Related to the removal of inferred route names, matchers that are passed in to c #### `CallLog` -Previously items in the call history were returned as `[url, options]` arrays, with a few additional properties added. Now they are returned as objects - `CallLog`s - that contain all information about the call and how it was handled. +Previously items in the call history were returned as `[url, options]` arrays, with a few additional properties added. Now they are returned as objects - `CallLog`s - that contain all information about the call and how it was handled. The `CallLog` interface is also the expected input for matcher functions and response builder functions. #### `done()` uses route names @@ -97,6 +97,7 @@ These are the new methods for resetting fetch mock to its default state. The nam A replacement for `sandbox()` that eschews all the weird wiring that `.sandbox()` used. Possibly not very useful for the average user, but I use it a lot in my tests for fetch mock, so it stays :-). + ## What's still to come There are a bunch of [breaking changes](https://github.com/wheresrhys/fetch-mock/issues?q=is%3Aopen+is%3Aissue+label%3A%22breaking+change%22) I'd like to ship before getting to v1.0.0. I also want to give users an incentive to migrate so there are a variety of new features I'd like to add and bugs to fix. Have a look at [the issues list](https://github.com/wheresrhys/fetch-mock/issues) and vote for any you like.