Ignore the extensions .ts and .tsx when importing them
#39
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
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.
When bumping eslint-plugin-import from 2.18.2 to a higher version, it complains about imported modules not having extensions. You may see the failed pipeline runs from Account, Marketplace and Contributor Portal.
The issue has been reported in eslint-plugin-import. The solution is provided based on this comment.
Tested with Account. It works as expected.
Note: We've planned further improvements for merging the rules in different libraries (CS-964). Let's do that step-by-step and make this change first. The merging can be the next step.