#329)  Resolves #328 ---- ## Behavior ### Before the change?  Test assertions of Responses from `fetch-mock` are done with `jest.toStrictEqual` with `JSON.stringify` ### After the change?  Test assertions of Responses from `fetch-mock` are done with `jest.toEqual` ### Other information  More context in octokit/core.js#588 ---- ## Additional info ### Pull request checklist - [x] Tests for the changes have been added (for bug fixes / features) - [ ] Docs have been reviewed and added / updated if needed (for bug fixes / features) - [ ] Added the appropriate label for the given change ### Does this introduce a breaking change?  Please see our docs on [breaking changes](https://github.com/octokit/.github/blob/main/community/breaking_changes.md) to help! - [ ] Yes (Please add the `Type: Breaking change` label) - [x] No If `Yes`, what's the impact: * N/A ### Pull request type `Type: Maintenance` ----

Replace toStrictEqual with JSON.stringify Response assertions with toEqual in rest.js #328

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Replace `toStrictEqual` with `JSON.stringify` Response assertions with `toEqual` in `rest.js` #328