fix: remove .js and .jsx extensions from lint script #16
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
Linter is not configured to lint .js and .jsx files and hangs when script it ran. ESLint should be configured to lint .js and .jsx files if they become used for more than config files.
hiyaryan
added
bug
|
@ishaan000 I figured out why the linter wasn't running so we don't need this "fix" anymore. It was due to the |
Actually it doesn't, because the file that has the error is ignored. |
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.
Linter is not configured to lint .js and .jsx files and hangs when script it ran. ESLint should be configured to lint .js and .jsx files if they become used for more than config files.