-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CLOSED] Move most inline jslint directives to config files #10796
Comments
I self reviewed a bit this and I saw an issue... |
Some things I've noticed during reviewing the 6500-lines diff (I probably shouldn't do this at 11pm...), in no particular order:
Also, I'm curious to hear which issue you found? |
Thank you for review.
For the issue I found, I changed a If we remove the inline jslint directives I suppose we loose the ability to lint our code with other tools. |
There may be some folks who want to run JSHint on the Brackets source, but the official tools are definitely JSLint, and, even more so, ESLint. |
LGTM from me. I'm of the opinion that we should completely ditch JSLint (and JSHint) in favor of ESLint making them just optional extensions downloadable from extension registry for those, who want them. Prerequisite for that would be of course shipping ESLint support in the core. |
I am all in favor of using ESLint exclusively both in the core and as the default extension. IMHO it's the current defacto tool and has the most adjustable rules and features. One idea would be also spinning the config off to its own module so it could be used for extension development too. |
LGTM. Thank you! |
Tuesday Aug 09, 2016 at 18:06 GMT
Originally opened as adobe/brackets#12661
Move most of the inline jslint directives inside
.brackets.json
and.eslintrc.json
.I've removed the
browser
directive too and so this PR supersedes #8658I left some directive like
regexp, forin
or some globals likeappshell, less
inline because seemed better for now.ficristo included the following code: https://github.com/adobe/brackets/pull/12661/commits
The text was updated successfully, but these errors were encountered: