mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
gecko-dev/python/mozlint/test/linters/regex.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

11 строки
242 B
YAML
Исходник Обычный вид История

Bug 1387862 - Lint python/mozlint yaml files. r=ahal We should have CI Lint YAML files in the tree. MozReview-Commit-ID: IMOKGhxKFJW --HG-- extra : rebase_source : 8c695dcb3a81b6683bc76ba663feeacb3126691e
2017-08-06 20:43:04 +03:00
---
Bug 1288432 - [mozlint] Use yaml for lint definitions and separate implementation of external linters, r=bc Rather than using .lint.py files that contain a LINTER object, linter definitions are now in standalone .yml files. In the case of external linters that need to run python code, the payload is now of the form: <module path>:<object path> The <module path> is the import path to the module, and <object path> is the callable object to use within that module. It is up to the consumer of mozlint to ensure the <module path> lives on sys.path. For example, if an external lint's function lives in package 'foo', file 'bar.py' and function 'lint', the payload would read: foo.bar:lint This mechanism was borrowed from taskcluster. MozReview-Commit-ID: AIsfbVmozy4 --HG-- rename : python/mozlint/test/linters/badreturncode.lint.py => python/mozlint/test/linters/badreturncode.yml rename : python/mozlint/test/linters/explicit_path.lint.py => python/mozlint/test/linters/explicit_path.yml rename : python/mozlint/test/linters/external.lint.py => python/mozlint/test/linters/external.yml rename : python/mozlint/test/linters/invalid_exclude.lint.py => python/mozlint/test/linters/invalid_exclude.yml rename : python/mozlint/test/linters/invalid_extension.lnt => python/mozlint/test/linters/invalid_extension.ym rename : python/mozlint/test/linters/invalid_include.lint.py => python/mozlint/test/linters/invalid_include.yml rename : python/mozlint/test/linters/invalid_type.lint.py => python/mozlint/test/linters/invalid_type.yml rename : python/mozlint/test/linters/missing_attrs.lint.py => python/mozlint/test/linters/missing_attrs.yml rename : python/mozlint/test/linters/missing_definition.lint.py => python/mozlint/test/linters/missing_definition.yml rename : python/mozlint/test/linters/raises.lint.py => python/mozlint/test/linters/raises.yml rename : python/mozlint/test/linters/regex.lint.py => python/mozlint/test/linters/regex.yml rename : python/mozlint/test/linters/string.lint.py => python/mozlint/test/linters/string.yml rename : python/mozlint/test/linters/structured.lint.py => python/mozlint/test/linters/structured.yml extra : rebase_source : bda3926712234123355c5af71c6453ce869b19fc
2017-06-02 16:49:26 +03:00
RegexLinter:
Bug 1387862 - Lint python/mozlint yaml files. r=ahal We should have CI Lint YAML files in the tree. MozReview-Commit-ID: IMOKGhxKFJW --HG-- extra : rebase_source : 8c695dcb3a81b6683bc76ba663feeacb3126691e
2017-08-06 20:43:04 +03:00
description: >-
Make sure the string foobar never appears in a js variable
file because it is bad.
Bug 1288432 - [mozlint] Use yaml for lint definitions and separate implementation of external linters, r=bc Rather than using .lint.py files that contain a LINTER object, linter definitions are now in standalone .yml files. In the case of external linters that need to run python code, the payload is now of the form: <module path>:<object path> The <module path> is the import path to the module, and <object path> is the callable object to use within that module. It is up to the consumer of mozlint to ensure the <module path> lives on sys.path. For example, if an external lint's function lives in package 'foo', file 'bar.py' and function 'lint', the payload would read: foo.bar:lint This mechanism was borrowed from taskcluster. MozReview-Commit-ID: AIsfbVmozy4 --HG-- rename : python/mozlint/test/linters/badreturncode.lint.py => python/mozlint/test/linters/badreturncode.yml rename : python/mozlint/test/linters/explicit_path.lint.py => python/mozlint/test/linters/explicit_path.yml rename : python/mozlint/test/linters/external.lint.py => python/mozlint/test/linters/external.yml rename : python/mozlint/test/linters/invalid_exclude.lint.py => python/mozlint/test/linters/invalid_exclude.yml rename : python/mozlint/test/linters/invalid_extension.lnt => python/mozlint/test/linters/invalid_extension.ym rename : python/mozlint/test/linters/invalid_include.lint.py => python/mozlint/test/linters/invalid_include.yml rename : python/mozlint/test/linters/invalid_type.lint.py => python/mozlint/test/linters/invalid_type.yml rename : python/mozlint/test/linters/missing_attrs.lint.py => python/mozlint/test/linters/missing_attrs.yml rename : python/mozlint/test/linters/missing_definition.lint.py => python/mozlint/test/linters/missing_definition.yml rename : python/mozlint/test/linters/raises.lint.py => python/mozlint/test/linters/raises.yml rename : python/mozlint/test/linters/regex.lint.py => python/mozlint/test/linters/regex.yml rename : python/mozlint/test/linters/string.lint.py => python/mozlint/test/linters/string.yml rename : python/mozlint/test/linters/structured.lint.py => python/mozlint/test/linters/structured.yml extra : rebase_source : bda3926712234123355c5af71c6453ce869b19fc
2017-06-02 16:49:26 +03:00
rule: no-foobar
Bug 1448417 - [mozlint] Remove ability to specify globs in an 'include' directive, r=egao There is only a single linter (test-disable.yml) that uses a glob in any include path, and that usage is easily replaced by using the 'extensions' key instead. Since globs in include directives aren't very useful, let's disallow them. This will allow us to simplify the 'filterpaths' logic quite substantially and make future refactorings in this area easier. Differential Revision: https://phabricator.services.mozilla.com/D6798 --HG-- extra : moz-landing-system : lando
2018-09-25 21:30:23 +03:00
include: ['.']
extensions: ['js', '.jsm']
Bug 1288432 - [mozlint] Use yaml for lint definitions and separate implementation of external linters, r=bc Rather than using .lint.py files that contain a LINTER object, linter definitions are now in standalone .yml files. In the case of external linters that need to run python code, the payload is now of the form: <module path>:<object path> The <module path> is the import path to the module, and <object path> is the callable object to use within that module. It is up to the consumer of mozlint to ensure the <module path> lives on sys.path. For example, if an external lint's function lives in package 'foo', file 'bar.py' and function 'lint', the payload would read: foo.bar:lint This mechanism was borrowed from taskcluster. MozReview-Commit-ID: AIsfbVmozy4 --HG-- rename : python/mozlint/test/linters/badreturncode.lint.py => python/mozlint/test/linters/badreturncode.yml rename : python/mozlint/test/linters/explicit_path.lint.py => python/mozlint/test/linters/explicit_path.yml rename : python/mozlint/test/linters/external.lint.py => python/mozlint/test/linters/external.yml rename : python/mozlint/test/linters/invalid_exclude.lint.py => python/mozlint/test/linters/invalid_exclude.yml rename : python/mozlint/test/linters/invalid_extension.lnt => python/mozlint/test/linters/invalid_extension.ym rename : python/mozlint/test/linters/invalid_include.lint.py => python/mozlint/test/linters/invalid_include.yml rename : python/mozlint/test/linters/invalid_type.lint.py => python/mozlint/test/linters/invalid_type.yml rename : python/mozlint/test/linters/missing_attrs.lint.py => python/mozlint/test/linters/missing_attrs.yml rename : python/mozlint/test/linters/missing_definition.lint.py => python/mozlint/test/linters/missing_definition.yml rename : python/mozlint/test/linters/raises.lint.py => python/mozlint/test/linters/raises.yml rename : python/mozlint/test/linters/regex.lint.py => python/mozlint/test/linters/regex.yml rename : python/mozlint/test/linters/string.lint.py => python/mozlint/test/linters/string.yml rename : python/mozlint/test/linters/structured.lint.py => python/mozlint/test/linters/structured.yml extra : rebase_source : bda3926712234123355c5af71c6453ce869b19fc
2017-06-02 16:49:26 +03:00
type: regex
payload: foobar