зеркало из https://github.com/mozilla/gecko-dev.git
10f8b7e161
While --fix previously worked with eslint, it is now more official (will show up in the |mach lint --help|). ESlint is still the only thing that implements it, but we can implement it for flake8 using the `autopep8` module. --edit is a new concept that will open an editor for each failing file to let you fix the errors manually. For now it is very naive (just opens the file), and is only really useful if you have an editor integration for the linter(s). But in the future I'd like to have editor-specific implementations for this. For example, with vim, we can use -q to pass in an error file that will start the editor pre-populated with a list of all errors that can then be easily jumped to. Other editors may just open up to the line containing the error. --fix and --edit can be used in conjunction with one another. Doing that means only errors that can't be fixed automatically will show up in your editor. MozReview-Commit-ID: 5JJJhMIrMIB --HG-- extra : rebase_source : 2f78a77a91133d7fcc5620ecd5caa500decbce1b |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozversioncontrol/mozversioncontrol | ||
| README | ||
| mach_commands.py | ||
| moz.build | ||
README
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025