fix: resolve TypeScript and Jest test issues in transform tests #333
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
amirabbas-gh
force-pushed
the
fix_issue_332
branch
4 times, most recently
from
ec1ee2b to
9df34d2
Compare
…escript jscodeshift package
amirabbas-gh
force-pushed
the
fix_issue_332
branch
from
9df34d2 to
8033306
Compare
amirabbas-gh
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📚 Description
This PR addresses multiple issues related to TypeScript errors, Jest test failures, and incorrect fixture names in transform tests. The main updates include:
require.requireActualin multiple transform testsjscodeshiftto the latest versionThese changes ensure that all affected tests run correctly without TypeScript or Jest errors.
🔗 Linked Issue
🧪 Test Plan
jscodeshiftand verified that all transforms still function correctly.