Unresolved reference
Reports references in the code that cannot be resolved to any declaration (for example, a method reference or a constant reference). Unresolved references often occur because of typos and can lead to runtime errors: NoMethodError, NameError, and so on.
When looking for a declaration, the receiver type (explicit or typed, resolve) is checked first. If there is no matching declaration found on the receiver, any matching declaration from the project (implicit or text-based, resolve) is accepted.
By default, a warning arises when there are no matching declarations irrespective of the receiver, i.e. implicit resolve fails.
Use the Report unresolved references on typed receivers checkbox to show warnings when there are no matching declarations on the receiver.
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.
RubyResolve- 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 ID: RubyResolve
Inspection options
Here you can find the description of settings available for the Unresolved reference inspection, and the reference of their default values.
- Report unresolved references on typed receivers
Option ID:
warnImplicitResultsDefault 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: |