-
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] Switching to ESLint #10331
Comments
Comment by ficristo I've a biased opinion since I don't like particularly JSLint, but if we want it still in core it should be at the least updated. |
Comment by abose Modified 3. We could default to ESLint only and provide a preference to enable JSLint also. |
Comment by zaggino Submitted a PR adobe/brackets#11988 |
Comment by tclzcja Since the brackets-shell ticket has been merged, does that mean ESLint will be formally included in Brackets 1.8 release? Thank you! |
Comment by ficristo
|
Comment by petetnt What's the status of this? |
Comment by zaggino I can setup a PR for "Integrate ESLint to Brackets core" if desired. |
Comment by petetnt
|
Comment by petetnt Shipped in 1.11. |
Issue by petetnt
Tuesday Dec 08, 2015 at 12:21 GMT
Originally opened as adobe/brackets#11984
Branched/continued from #11644, #11693
This issue was created to track down moving to ESLint separately from the existing PR (and the general ES6 support)
@
zaggino (Eslint adobe/brackets#11693 (comment))The integration part should be easy but what about the third box? Possible options include:
@
abose@
ficristo@
MarcelGerberThe text was updated successfully, but these errors were encountered: