Use named getter
Reports calls to generated componentN() methods on Kotlin data classes from Java code.
Kotlin data classes automatically generate positional component1(), component2(), and similar methods for destructuring. Calling them directly from Java is fragile: the mapping between index and property is not obvious, and the calls break silently if properties are reordered. Using the named property getter is clearer and refactoring-safe.
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.
UseNamedGetter- 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: UseNamedGetter
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: |