fix(babel-plugin-jest-hoist): allow using module wrapper arguments in hoisted mock factory function #10903
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.
Summary
This allows several things. My specific case is using the content of a file as the return value for a mocked function:
The test is located inside a Yarn workspace, and for complicated reasons I have to execute
jest
from the root of the repository. As far as I can tell, this is the only way I can avoid letting the test know about its own directory path in the repo.Test plan
To be honest, I'm just doing what @SimenB told me would solve my problem.
I applied this patch to my own repo, and it works. Does it make sense to document this further?