Ability to save after .next

[lourd]

Currently saving a point in the history of a mock saga is only available before a call to .next, giving the next input into the saga. It would be very helpful if you could also save after a call to .next, before the effect assertion. Attempting to do so with v2.2.0 throws a TypeError exception, e.g. ...next(...).save(...).call is not a function.

[jfairbank]

Hi, @lourd! This makes sense to make available after a call to next if possible. I'll get to it soon unless you want to take a stab at a PR for it.

[marifehe]

Hey @jfairbank , I'd like to contribute with a PR for this. I haven't done many PRs to real open source serious projects (other than mine), so I think this is a good one to start with.

I've been checking the code and I don't think the issue is that save cant be called after a call to next, but instead that save doesn't have the effects available as methods, but only the testSaga Api methods (next,back, finish, etc etc). That's why the error saying call is not a function.
So, the fix should be making the effects available after a call to save. Is that something that makes sense to you? If so, I'm very happy to put the PR. :)