Exhaustiveness check for switch expressions
Reports switch expressions that do not cover all possible outcomes of the matched expression.
Groovy does not require that switch expression must be exhaustive. It acts as if an implicit default -> null branch is inserted. It may cause unexpected nulls if a developer forgets to insert necessary case branches.
Example:
Locating this inspection
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
GrSwitchExhaustivenessCheck- Via Settings dialog
Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.
Inspection options
Here you can find the description of settings available for the Exhaustiveness check for switch expressions inspection, and the reference of their default values.
- Report unmatched 'null'
Default value:
Not selected
Suppressing Inspection
You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: |