You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting up mocks without any argument expectations, I get the following message:
Unintended use: Only use default value in combination with .calledWith(..), or use standard mocking without jest-when.
However, I would really rather have a single syntax for mock setups across the whole solution.
I understand that it does not play well linguistically with when, but perhaps a more neutral alias can be exposed, like setupMock, which would not produce this warning.
In fact, I am trying to migrate from a homemade solution where the function is named just that: setupMock.
The text was updated successfully, but these errors were encountered:
When setting up mocks without any argument expectations, I get the following message:
Unintended use: Only use default value in combination with .calledWith(..), or use standard mocking without jest-when.
However, I would really rather have a single syntax for mock setups across the whole solution.
I understand that it does not play well linguistically with
when
, but perhaps a more neutral alias can be exposed, likesetupMock
, which would not produce this warning.In fact, I am trying to migrate from a homemade solution where the function is named just that:
setupMock
.The text was updated successfully, but these errors were encountered: