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.

Sign up for GitHub

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

Jump to bottom

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

Merged
merged 1 commit into from Jan 9, 2019
Merged

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

merged 1 commit into from Jan 9, 2019

Commits on Jan 9, 2019

  1. Change recommended configuration so that the `typescript-eslint-parse… 

    …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
    @fuller
    fuller committed Jan 9, 2019
    Copy the full SHA
    5cd4eb0 View commit details
    Browse the repository at this point in the history