mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-23 10:15:41 +00:00
2f6a0dfa63
This formatter is useful for triaging paths when enabling new linters or expanding existing ones. It works well with the -n/--no-filter option. For example, if I wanted to look for candidates of new directories to enable the codespell linter on, I could run: ./mach lint -l codespell -nf summary This will print something like: accessible: 429 dom: 142 layout: 15 testing: 53 etc.. If desired, you can also specify a depth by setting MOZLINT_SUMMARY_DEPTH. A depth of 2 means results will be aggregated further down, e.g: accesible/build: 129 accesible/ipc: 300 dom/indexedDB: 100 dom/workers: 42 etc.. The depth is always relative to the common path prefix of all results, so running: ./mach lint -l codespell -nf python/mozbuild Would expand all the directories under python/mozbuild (not topsrdir). MozReview-Commit-ID: OiihLTpULA --HG-- extra : rebase_source : eaaabc1d5cdc8e3942808d01b24e22081fea752e |
||
---|---|---|
.. | ||
devtools/migrate-l10n | ||
l10n/fluent_migrations | ||
mach | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozterm | ||
mozversioncontrol | ||
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