Uh oh!
There was an error while loading. Please reload this page.
Fix absolute paths issue in Jest - #7822
Merged
Merged
Conversation
robertvansteen
requested review from
ianschmitz, iansu, mrmckeb and petetnt
as code ownersOctober 13, 2019 19:27
ianschmitz
approved these changes
Oct 14, 2019
iansu
commented
Oct 14, 2019
Contributor
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
This PR fixes#7818, by fixing the entry added to Jest's
moduleNameMapperthat unintentionally matched with paths that did not start withsrc.