Allow shouldIgnoreMissing() to behave in a recursive fashion #1097
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.
When setting up lazy mocks I often run into issues where the test just breaks at the second link and I end up having to explicitly set expectations for the functions anyway, which requires knowledge about implementation details of things that are not relevant for the given test. This PR aims to solve that by allowing for
shouldIgnoreMissing()
to behave in a recursive fashion.code:
Before:
After: