Support calling a route n times

[wheresrhys]

Support calling a route n times

[wheresrhys]

That'll work, but limiting responding to n calls I think is a nice feature to add anyway

[wheresrhys]

done

[wheresrhys]

Easiest way would be to manage the state outside the mock.

let called = false;
fetchMock.mock('http://test.com', function () {
   if (called) {
     return {valid: 'response', after: 'error'};
   }
   called = true;
   return 500;
})

(If that doesn't work it's a bug, so let me know and I'll fix it if it fails)

If you have any thoughts on what a nicer API for this sort of behaviour would look like I'm happy to consider adding it.

[wheresrhys]

I could accept an additional parameter specifying the number of times a mock should respond, but I'd be concerned about adding more complexity to the API and docs (which are already long enough IMO)

[queicherius]

Yeah the managing the state outside works, I was just wondering if I was overlooking something 😄

The times parameter would make this easier, but I am not sure if that usecase is so common that it justifies it.

[wheresrhys]

It's a feature I'd like to add anyway, though it does get a little bit tricky to implement in some of the details because it's permissable for calls to fall through from one route to another. Will have a go

[wheresrhys]

Some failing tests written https://github.com/wheresrhys/fetch-mock/compare/times, but the edge cases are quite problematic

[amit1911]

i have the same requirement and i am calling fetchMock.restore() before mocking another call to the same url and it seems to be working fine. Is this also okay?

[montogeek]

I would like to ask for this feature too, we can use something similar to Nock https://github.com/node-nock/nock#repeat-response-n-times

For example, this is useful when testing polling requests, first 3rd requests are the same, but 4th is different