Consider switching from jest-fetch-mock to fetch-mock
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 13
- Avg merge
- 15h 15m
- Merged PRs (30d)
- 3
Description
We both ran into the issue of order in which you mock URLs which is super annoying. This issue was reported here, and as no real solution seems to exist, people suggested to use fetch-mock instead.
Now, it also seems empty response bodies are not supported by jest-fetch-mock so I suggest we give fetch-mock a try?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the current jest-fetch-mock setup and tests, then compare the fetch-mock behavior against the URL-mocking order and empty-response cases described in the issue. Review the linked reports and existing test suite; done means the project uses fetch-mock without regressions and those cases are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100