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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(jest-resolve-dependencies): resolve mocks as dependencies #8952
fix(jest-resolve-dependencies): resolve mocks as dependencies #8952
Changes from 4 commits
6da2875
5cce42e
014d4de
4cebe1b
d7e327c
39cb1ad
651b27c
8137d38
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if we still need two code paths to resolve a mock. I'm unsure what this line is even for, maybe virtual mocks that do not have a real module counterpart?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not entirely sure but I assumed so, as the case where an error is thrown there expects the name to exist in (i think) the metadata but not be in the filesystem.
I left a note for prosterity in this commit: 8137d38
I could try to get to the bottom of this in this PR since it's pretty related, would that be a good idea?
If you do, is there a way I could figure out if this code is exercised in the test suite?