[CLOSED] Switching to ESLint #10331
Description
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)
- Update Brackets core code to ESLint (done in [CLOSED] Dilato: Core: The rename function doesn't work from the second time #11693)
- Integrate ESLint to Brackets core
@zaggino (Eslint adobe/brackets#11693 (comment)) - Decide what to do with the existing linter (JSLint)
The integration part should be easy but what about the third box? Possible options include:
- Make ESLint the preferred linter and let the user use JSLint if the user decides to do so (confusing to those who have just used JSLint in the past)
- Make ESLint the preferred linter and remove JSLint altogether (spinning it to non-core extension) (similar issues as above)
- Just let them exist side by side and the let the user configure the settings (most confusing as files get linted twice?)
- Provide UI to select the preferred linter on first launch of Brackets 1.x (most user friendly, needs UI work etc.)
@abose@ficristo@MarcelGerber