-
Notifications
You must be signed in to change notification settings - Fork 70
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
import_all does not recognise unused JSX classes #85
Comments
if you run 'ecmaFeatures': {
'jsx': true
}, in eslint 2, this is {
"parserOptions": {
"ecmaFeatures": {
"jsx": true
}
}
} But I'm not actually sure. It doesn't work for me either, and I have eslint 1.10.1 installed. |
Yep, it does catch it when just running |
Is it possible that you have two different |
It turns out that we broke this a while ago in de3c9ee. Look at what eslint outputs for the
The jsx plugin puts the variable in single quotes. I'll fix this and publish a new version soon. |
Ah! My bad. I'll look into submitting a PR to the React plugin to make this consistent with ESLint. |
Ah, that would be great! |
Actually, it seems that most ESLint rules use single quotes. So perhaps I'll submit a PR over there instead. |
While working on a different project that consumes the output of ESLint and some plugins, we noticed that the quote styles emitted by the no-undef rule was different than the quote styles emitted by some of the rules in our other plugins [0]. This inconsistency led to a small bug in our plugin, so I wanted to smooth things out a bit for future developers. To make things more consistent, my first inclination was to change the plugin to match ESLint's no-undef quote style, but upon investigation it seems that most of the core ESLint rules use single quotes instead of double quotes, so I decided to change this one to be more consistent. There may be other inconsistencies that are worth resolving, but this commit fixes the main pain point for me. [0]: Galooshi/import-js#85 (comment)
While working on a different project that consumes the output of ESLint and some plugins, we noticed that the quote styles emitted by the no-undef rule was different than the quote styles emitted by some of the rules in our other plugins [0]. This inconsistency led to a small bug in our plugin, so I wanted to smooth things out a bit for future developers. To make things more consistent, my first inclination was to change the plugin to match ESLint's no-undef quote style, but upon investigation it seems that most of the core ESLint rules use single quotes instead of double quotes, so I decided to change this one to be more consistent. There may be other inconsistencies that are worth resolving, but this commit fixes the main pain point for me. Fixes eslint#4845 [0]: Galooshi/import-js#85 (comment)
While working on a different project that consumes the output of ESLint and some plugins, we noticed that the quote styles emitted by the no-undef rule was different than the quote styles emitted by some of the rules in our other plugins [0]. This inconsistency led to a small bug in our plugin, so I wanted to smooth things out a bit for future developers. To make things more consistent, my first inclination was to change the plugin to match ESLint's no-undef quote style, but upon investigation it seems that most of the core ESLint rules use single quotes instead of double quotes, so I decided to change this one to be more consistent. There may be other inconsistencies that are worth resolving, but this commit fixes the main pain point for me. [0]: Galooshi/import-js#85 (comment) (fixes eslint#4845)
While working on a different project that consumes the output of ESLint and some plugins, we noticed that the quote styles emitted by the no-undef rule was different than the quote styles emitted by some of the rules in our other plugins [0]. This inconsistency led to a small bug in our plugin, so I wanted to smooth things out a bit for future developers. To make things more consistent, my first inclination was to change the plugin to match ESLint's no-undef quote style, but upon investigation it seems that most of the core ESLint rules use single quotes instead of double quotes, so I decided to change this one to be more consistent. There may be other inconsistencies that are worth resolving, but this commit fixes the main pain point for me. [0]: Galooshi/import-js#85 (comment)
While working on a different project that consumes the output of ESLint and some plugins, we noticed that the quote styles emitted by the no-undef rule was different than the quote styles emitted by some of the rules in our other plugins [0]. This inconsistency led to a small bug in our plugin, so I wanted to smooth things out a bit for future developers. To make things more consistent, my first inclination was to change the plugin to match ESLint's no-undef quote style, but upon investigation it seems that most of the core ESLint rules use single quotes instead of double quotes, so I decided to change this one to be more consistent. There may be other inconsistencies that are worth resolving, but this commit fixes the main pain point for me. [0]: Galooshi/import-js#85 (comment)
While working on a different project that consumes the output of ESLint and some plugins, we noticed that the quote styles emitted by the no-unused-vars rule was different than the quote styles emitted by some of the rules in our other plugins [0]. This inconsistency led to a small bug in our plugin, so I wanted to smooth things out a bit for future developers. To make things more consistent, my first inclination was to change the plugin to match ESLint's no-unused-vars quote style, but upon investigation it seems that most of the core ESLint rules use single quotes instead of double quotes, so I decided to change this one to be more consistent. There may be other inconsistencies that are worth resolving, but this commit fixes the main pain point for me. [0]: Galooshi/import-js#85 (comment)
) While working on a different project that consumes the output of ESLint and some plugins, we noticed that the quote styles emitted by the no-undef and no-unused-vars rule was different than the quote styles emitted by some of the rules in our other plugins [0]. This inconsistency led to a small bug in our plugin, so I wanted to smooth things out a bit for future developers. To make things more consistent, my first inclination was to change the plugin to match ESLint's no-undef and no-unused-vars quote style, but upon investigation it seems that most of the core ESLint rules use single quotes instead of double quotes, so I decided to change these rules to be more consistent. There may be other inconsistencies that are worth resolving, but this commit fixes the main pain point for me. [0]: Galooshi/import-js#85 (comment)
) While working on a different project that consumes the output of ESLint and some plugins, we noticed that the quote styles emitted by the no-undef and no-unused-vars rule was different than the quote styles emitted by some of the rules in our other plugins [0]. This inconsistency led to a small bug in our plugin, so I wanted to smooth things out a bit for future developers. To make things more consistent, my first inclination was to change the plugin to match ESLint's no-undef and no-unused-vars quote style, but upon investigation it seems that most of the core ESLint rules use single quotes instead of double quotes, so I decided to change these rules to be more consistent. There may be other inconsistencies that are worth resolving, but this commit fixes the main pain point for me. [0]: Galooshi/import-js#85 (comment)
While working on a different project that consumes the output of ESLint and some plugins, we noticed that the quote styles emitted by the no-undef and no-unused-vars rule were different than the quote styles emitted by some of the rules in our other plugins [0]. This inconsistency led to a small bug in our project, so I wanted to smooth things out a bit for future developers. To make things more consistent, my first inclination was to change the plugin to match ESLint's no-undef and no-unused-vars quote style, but upon investigation it seems there was a fair amount of inconsistency in ESLint rules: some used double quotes, some used single quotes, and others used backticks. I decided to convert all of these to single quotes to be more consistent. There may be others that I have missed, but this commit should get the bulk of them. [0]: Galooshi/import-js#85 (comment)
I run into this frequently now, since I use Sublime Text which only supports import_all. It would never recognise
<Button>
as an unused variable.The text was updated successfully, but these errors were encountered: