This setting specifies a list of path patterns to exclude from linting.
If there is only a single pattern, the value may be a string.
Otherwise it must be an array of patterns.

Patterns are matched against a file’s absolute path with all symlinks/shortcuts resolved.
This means to match a filename, you must match everything in the path before the filename.
For example, to exclude any python files whose name begins with “foo”, you would use this pattern:

{"excludes":"*/foo*.py"}

The default value is an empty array.
Untitled views can be ignored with <untitled>,
and you can use ! to negate a pattern.
Note that Settings Expansion can be used here as well.

This defines a post filter to suppress some problems a linter might report.
(Useful if the linter cannot be configured very well.)

The value may be a string or an array of strings. Each string is handled as
a case-insensitive regex pattern, and then matched against the error type, code (or rule), and message of a particular lint problem. If it matches, the lint error will be thrown away.

Note

This will completely supress the matching errors. If you only want to visually demote some errors, take a look at the styles section below.

Be aware of special escaping since what you’re writing must be valid JSON.

Technical note: For each reported problem we construct a string “<error_type>: <error_code>: <error_message”. We then match each regex pattern against that virtual line. We keep the error if none of the patterns match, otherwise we keep it.