Inspection profiles

base

The base node lets you specify the profile that will serve as a basis for your profile configuration. You can use either a file path or a name:

The name key supports the following values:

If the name declaration is missing, Qodana will employ the Project Default profile, so all settings applied in your custom profile will override such settings contained in Project Default.

name

Arbitrary name for your profile.

groups

The groups node is a list of user-defined groups. Here, you can combine inspection categories and single inspections, and then configure their usage in the inspections node.

Each group definition can include or exclude other groups or single inspections.

You can use the exclamation mark character (!) to negate a group or a category. For example, you can exclude a specific category usage in a group that will be included.

Here is the sample containing the EnabledInspections group defined by a user:

This sample contains the following elements:

inspections

Using inspections, you can:

• Enable or disable a specific group or an inspection,

• Define the order of applying these settings,

• Define the paths or scopes to be ignored by the specific group or the inspection,

• Customise severity for specific inspections or inspection groups,

• Configure inspection options.

This sample contains several elements:

Example of import

Suppose, you have the foo.yaml and bar.yaml profiles.

The foo.yaml profile enables the Inspection1, Inspection2 and Inspection3 inspections:

The bar.yaml profile disables the Inspection1 inspection:

You can include these two files in the custom profile and disable Inspection2:

In this case, the effective profile configuration read by Qodana will look like this:

Exclude inspection

This lets you exclude the PhpDeprecationInspection inspection available in the Qodana for PHP linter:

Alternatively, you can exclude the PhpDeprecationInspection inspection using groups:

Exclude paths

You can use the ignore key to ignore specific scopes and paths while inspecting your code.

In the sample below, the vendor/** value employs glob patterns for ignoring the contents of the vendor directory contained in your project root.

The scope definition scope#file:*.js:testData//* ignores all files with the .js extension recursively contained in the testData/ directory.

Create profile

Using base, this configuration defines the empty profile, and then it includes only the Java/Data flow inspection group from the Qodana for JVM linter.

As an alternative to base, you can use ALL in the groups property:

Override profile

You can exclude inspection categories from the qodana.starter profile that are not related to the Qodana for .NET linter.

Filter by severity

This sample includes all inspections with the WEAK WARNING severity level while inspecting Java code:

Override severity

You can override the severity levels for existing inspections. Here’s how you can assign the WARNING severity level to the JavadocReference inspection:

Override options

Specific inspections offer configurable options. For example, the JvmCoverageInspection inspection offers the classThreshold, methodThreshold, and warnMissingCoverage options.

To discover this, configure this inspection in IntelliJ IDEA and then export the profile. Here is a profile example for the JvmCoverageInspection inspection:

This sample demonstrates how you can configure the inspection options in your custom profile: