Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change recommended configuration to use plugin-specific parser rather than changing global parser #12

Merged
merged 1 commit into from Jan 9, 2019

Conversation

fuller
Copy link
Contributor

@fuller fuller commented Jan 9, 2019

We noticed some unrelated errors when changing the global parser, so this was the fix that worked in our case and follows the structure from the eslint-plugin-import docs to change the parser for import and restrict it to .ts and .tsx files.

https://github.com/benmosher/eslint-plugin-import#importparsers

…r` is only used for `import` plugin rather than globally

Presumably this is being used while people convert over to TypesScript, so scoping it to the individual plugin settings can prevent unrelated issues from popping up. We noticed some additional errors when changing the global parser, so this was the fix that worked in our case and follows the structure from the`eslint-plugin-import` docs https://github.com/benmosher/eslint-plugin-import#importparsers
@alexgorbatchev
Copy link
Collaborator

Thank you for taking time to submit the PR!

@alexgorbatchev alexgorbatchev merged commit 55e37e4 into import-js:master Jan 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants