Make sinon.stub() mock implementation when nothing is returned (& other tweaks) #291
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cc @lencioni @catc
In some recent PRs I noticed that
sinon.stub(a, b)
is transformed intojest.spyOn(a, b).mockClear()
but it also needs a.mockImplementation()
in the general case (when there's not a.return()
or.returnArg()
). So I've added that.Additionally, I read sinon's doc on
stub()
andspy()
and we don't need/implementstub(a)
(which mocks all keys in the object) so I'm marking that as unsupported (it's not advised even from sinon's doc).I added a warning when there's more than 3 arguments (which doesn't seem to be valid, AFAICT).
I also changed
jest.fn().mockImplementation(...)
to justjest.fn(...)
because it's equivalent and shorter.