Ignoring Issues with Qlty CLI

To fine tune your analysis results, you can ignore issues within your source code or through rules in your qlty.toml project configuration file.

Mute comments

Qlty CLI supports using mute comments in your source code files to ignore issues on a line, within a block of code, or for an entire file.

Adding [[exclude]] rules in qlty.toml

Qlty CLI also allows a simple way to exclude certain plugins from running on a set of files in your project configuration file (.qlty/qlty.toml). Each [[exclude]] block can specify conditions by plugins and file patterns. Qlty will avoid running the given plugins on files that match the given patterns or ignore any issues matching the plugins and file patterns.

Examples:

1
# Exclude eslint from running on files in remix/app/components/ui/
2
[[exclude]]
3
plugins = ["eslint"]
4
file_patterns = ["remix/app/components/ui/**"]

Adding [[triage]] rules in qlty.toml

Qlty CLI also allows a highly flexible way to suppress issues in your project configuration file (.qlty/qlty.toml). Each [[triage]] block can specify match conditions by plugins, rules, file globs, and levels. If an issue matches all the specified conditions, it will be ignored.

Examples:

1
# Ignore the eslint react/prop-types check only in remix/app/components/ui/
2
[[triage]]
3
match.rules = ["eslint:react/prop-types"]
4
match.file_patterns = ["remix/app/components/ui/**"]
5
set.ignored = true

1
# Ignore all rubocop issues at "low" level
2
[[triage]]
3
match.plugins = ["rubocop"]
4
match.levels = ["low"]
5
set.ignored = true

Reviewing ignored issues

Issues that have been ignored in the project configuration file (.qlty/qlty.toml) are surpressed at generation time and cannot be viewed in the Qlty web application.

See Also

• Excluding Files
• Triaging Issues with Qlty Cloud