When both kotlin.coroutine.coroutineContext and kotlinx.coroutines.CoroutineScope.coroutineContext can be present in the code, it can lead to confusion and potential bugs.

The kotlinx.coroutines library provides currentCoroutineContext() function as a clearer alternative that should be preferred even when there is no explicit clash.

See the documentation for kotlin.coroutine.coroutineContext and kotlinx.coroutines.currentCoroutineContext for more details.

Example:

  suspend fun getCurrentJob(): Job? {
    return coroutineContext[Job]
  }

After the quick-fix is applied:

  suspend fun getCurrentJob(): Job? {
    return currentCoroutineContext()[Job]
  }