Andrew Halberstadt f297ed8c8f Bug 1373368 - [mozlint] Raise if a non-existant path is specified in a lint config, r=standard8 ...

Since I left the next two patches to bitrot, I realized that a path I had added
didn't exist anymore. We should definitely error out if non-existant paths are
specified, otherwise the lists will become outdated and it will be possible to
accidentally disable linting on some files.

I discovered a few instances of this already in our existing definitions.

MozReview-Commit-ID: 8jsTKLI0nFE

2018-03-29 14:50:17 -04:00

..

badreturncode.yml

…

explicit_path.yml

…

external.py

…

external.yml

…

invalid_exclude.yml

…

invalid_extension.ym

…

invalid_include.yml

…

invalid_support_files.yml

…

invalid_type.yml

…

missing_attrs.yml

…

missing_definition.yml

…

non_existing_exclude.yml

…

non_existing_include.yml

…

non_existing_support_files.yml

…

raises.yml

…

regex.yml

…

setup.yml

…

setupfailed.yml

…

setupraised.yml

…

slow.yml

…

string.yml

…

structured.yml

…

support_files.yml

…