v5

[wheresrhys]

• deprecate greed option
• implement new catch method
• deprecate complex config
• deprecate useNonGlobalFetch
• Global config for sendAsJSON
• Accept a Response object as a response in .mock() waiting on default to 200 response status node-fetch/node-fetch#132
• Expose fetch-mock's mockResponse() internal as a utility
• reset and restore return fetchMock instance
• deprecate reMock
• write upgrade notes
• deprecate accepting an array of routes
  • bind fetchMock.mock to fetchMock so can be passed into [].map()
• regex call matching Add filterCalls(), testCalls() #83 ???
• API change to mock(matcher, response, options)
  • get, post, put, delete, head shorthands
  • Configure number of times a mock can be used
  • mockOnce, getOnce, postOnce etc

[montogeek]

Shorthands! 👍

[wheresrhys]

mainly done. Gonna go for a release

[wheresrhys]

#110

[wheresrhys]

Ah no, blocked by node-fetch/node-fetch#132

[montogeek]

Just voted it :)

[montogeek]

I just saw your commit about shorthands, what you think about PATCH (capitalized)?
Related: JakeChampion/fetch#37 and https://fetch.spec.whatwg.org/#methods

[wheresrhys]

If you want to add a PR for it after v5 is released I'll consider it if other users 👍 it. get, post, put, delete and head are the 'Big 5' methods, and as long as fetch-mock provides an api to target other methods I'm reasonably comfortable with leaving the shorthand coverage at that. I might add OPTINS too.

What's your use case for PATCH? I've never had to use it

[montogeek]

Sure, I will add it :)
I've used PATH neither, just thinking about giving more options to the users