Back to Intellij Community

UselessCallOnFlow

plugins/kotlin/code-insight/descriptions/resources-en/inspectionDescriptions/UselessCallOnFlow.html

2025.3-rc-21.0 KB
Original Source

Reports redundant calls on Flows from kotlinx.coroutines library.

This inspection detects two kinds of redundancy:

  • Redundant filter… calls on already filtered Flows. Functions such as filterNotNull() or filterIsInstance have sense only when they are called on receivers that have types distinct from the resulting one. Otherwise, such calls can be omitted as the result will be the same.
  • Redundant mapNotNull calls. mapNotNull is redundant when the transformation result is already guaranteed to be non-nullable. In that case, the NotNull suffix can be dropped (e.g., mapNotNullmap).

A quick-fix is available to omit the redundant call or replace it with a simpler alternative.

Examples:

fun test(flow: Flow<String>) {
      val x = flow.filterNotNull() // can be simplified to 'flow'
      val y = flow.filterIsInstance<String>() // can be simplified to 'flow'
  }
fun test(flow: Flow<Int>) {
      val x = flow.mapNotNull { it + 1 } // can be replaced with 'map'
  }