Disable and suppress inspections
Some inspections may report problems that you currently do not want to see. In this case, you can disable or suppress them.
When you disable an inspection, you turn it off. It means that the code analysis engine stops searching project files for the problem that this inspection is designed to detect. Note that when you disable an inspection, you disable it in the current inspection profile; it remains enabled in other profiles.
Most inspections in RustRover can be disabled. However, some inspections will keep highlighting your code regardless of the settings. For example, syntax errors are always highlighted.
Press CtrlAlt0S to open settings and then select Editor | Inspections.
Locate the inspection you want to disable, and clear the checkbox next to it.
Apply the changes and close the dialog.
Place the caret at the highlighted line and press AltEnter (or click
to use the intention action).
Click the arrow next to the inspection you want to disable, and select Disable inspection.
In the Inspection Results tab of the Problems tool window (appears once you run code analysis), right-click the inspection you want to disable and select Disable inspection.
Click
to hide the disabled inspection alerts.
When you suppress an inspection, the code analysis engine doesn't highlight the problem found by this inspection in the specific piece of code. You can also suppress all inspections in the current item.
Most inspections in RustRover can be suppressed. However, some inspections do not have this option. For example, syntax errors are always highlighted in the editor regardless of the settings.
Place the caret at the highlighted line and press AltEnter (or click
to use the intention action).
Click the
button next to the inspection you want to suppress and select the suppress action according to the required scope.
tip
To suppress an inspection for a piece of code, RustRover precedes it either with the
#[allow(<inspection name>)]
attribute (for lint inspections) or the//noinspection
comment (for the rest).
In the Inspection Results tab of the Problems tool window (appears once you run code analysis), right-click the inspection you want to suppress and select the necessary suppress action.
tip
To suppress an inspection for a piece of code, RustRover precedes it either with the
#[allow(<inspection name>)]
attribute (for lint inspections) or the//noinspection
comment (for the rest).
To re-enable a suppressed inspection, delete the annotation or the comment that the IDE has added before the selected symbol.
Inspections have severities according to which they highlight code problems in the editor. You can quickly disable code highlighting for an inspection without opening the settings. In this case, the inspection remains enabled and provides a fix, but the severity changes to No highlighting (fix available).
Place the caret at a code element highlighted by an inspection in the editor and press AltEnter.
A list with available fixes and context actions opens. Locate the inspection fix that is marked with
.
Click the
button next to the fix to open the inspection's options and select Disable highlighting, keep fix.
If you want to restore the highlighting, press CtrlAlt0S to open the IDE settings and select Editor | Inspections. Find the necessary inspection in the list and change its severity as you like. For more information, refer to Change inspection severity in all scopes.
By default, RustRover highlights all detected code problems. Hover over the widget in the top-right corner of the editor and select another level from the Highlight list:
None: turn highlighting off.
Syntax: highlight syntax problems only.
All Problems: (default) highlight syntax problems and problems found by inspections.
You can also change the highlighting level from the main menu. Select Code | Analyze Code | Configure Current File Analysis or press CtrlAltShift0H.
Thanks for your feedback!