fix(@jest/transform): throw better error if an invalid return value if encountered #12764
Conversation
This file contains 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
mrazauskas
commented
Apr 28, 2022
mrazauskas
force-pushed
the
fix-better-InvalidReturnValueError
branch
from
52bacd2
to
cf82664
Compare
F3n67u
pushed a commit
to F3n67u/jest
that referenced
this pull request
May 2, 2022
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
From #12750 (comment)
Summary
As it was mentioned in the comment: if a transformer returns an invalid value, it would be good to include transformer’s path in the error message. Link to Upgrade Guide is also a useful detail.
Test plan
Green CI.