[cleanup] remove legacy path condition in jest preprocessor #31361
+45
−48
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 PR removes a condition that looks legacy inside Jest preprocessor script.
How I happened upon this:
Running
yarn test
on a fresh clone of the repository, I ran into Jest errors suggesting files were not transformed properly by babel.I tracked it down to a condition in
scripts/jest/preprocessor.js
:I had cloned the repo on my machine inside a
third_party/react
directory, causing this condition to always be false 🥲 .How did you test this change?
Research done:
third_party
directory, and it was insidenode_modules
(hence already ignored by babel transforms).git log --diff-filter=ACDR -- '*third_party*'
.third_party
folder existed at some point in the codebase and was removed in commit 8b4ec79.Running
yarn test
before/after the change produces the same output in the general case.If running
yarn test
with a path likethird_party/react
, the command fails before this change and passes after.This seemed like a tiny fix so I did not open an issue.