Kotlin
Useless call on not-null type
Warning
New
Last modified: 03 December 2024Reports calls on not-null receiver that make sense only for nullable receiver.
Several functions from the standard library such as orEmpty()
or isNullOrEmpty
have sense only when they are called on receivers of nullable types. Otherwise, they can be omitted or simplified as the result will be the same.
Remove redundant call and Change call to … quick-fixes can be used to amend the code automatically.
Examples:
fun test(s: String) {
val x = s.orEmpty() // quick-fix simplifies to 's'
val y = s.isNullOrEmpty() // quick-fix simplifies to 's.isEmpty()'
}
- 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.
UselessCallOnNotNull
Inspection Details | |
---|---|
By default bundled with: | |
Can be installed with plugin: | Kotlin, 243.23126-IJ |
Thanks for your feedback!
Was this page helpful?