-firefox-dev To be explicit, if you're running this for mobile code, you should be using:
`mach eslint mobile/android` Using other paths may not read the configuration files correctly and the output may be unexpected. I'd recommend using eslint to help develop JS from now on. Note the list of ignored files [1] before assuming eslint has found all flaws in the code you've modified. There are some regressions with the HomeProvider code at present so you'll see some errors in `modules/HomeProvider.jsm` - ignore (or fix ;) those for now. I'll continue to fix warnings and enabling disabled rules gradually over time to make eslint more effective. By the way, thanks Nick! :D - Mike (:mcomella) [1]: https://mxr.mozilla.org/mozilla-central/source/mobile/android/.eslintignore On Thu, Jul 2, 2015 at 12:31 PM, Nicholas Alexander <[email protected]> wrote: > Hi folks, > > Building on the Loop team's blog posts and mcomella's initial code, I just > landed |mach eslint| on fx-team. > > Use it like |mach eslint PATH/TO/LINT| from topsrcdir or like |mach > eslint| in PATH/TO/LINT. To test it out, try |mach eslint > browser/components/loop|. > > File fall-out and feature requests blocking Bug 1177933, please. > > Yours, > Nick > > [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1177933 > > _______________________________________________ > mobile-firefox-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/mobile-firefox-dev > >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
