Is `ForbiddenMethodCall` expected to work? I have this config and it doesn’t seem to pick up on `run...

# detekt

[Kirill Zhukov]

Is ForbiddenMethodCall expected to work?
I have this config and it doesn’t seem to pick up on runBlocking calls in the codebase 👀

ForbiddenMethodCall:
  active: true
  methods:
      value: 'runBlocking'

[Kirill Zhukov]

Other rules seem to work in the same file

[Kirill Zhukov]

also tried fq kotlinx.coroutines.runBlocking

[Kirill Zhukov]

Even default method calls for println and print aren’t caught

[Sam]

Are you running detekt with type resolution turned on? Looks like type resolution is required for the ForbiddenMethodCall rule. https://detekt.dev/docs/gettingstarted/type-resolution

[Kirill Zhukov]

I am running detektMetadataCommonMain in the kmp project, does that enable type resolution?

[Atul Gupta]

In Gradle logs detekt prints if any rule is skipped due to type resolution or not
Log message: The rule 'UnnecessarySafeCall' requires type resolution but it was run without it

[Atul Gupta]

Put

detekt {
    debug = true
}

in detekt gradle config

[Kirill Zhukov]

Yeah, that’s exactly what I’m seeing The rule 'ForbiddenMethodCall' requires type resolution but it was run without it.

[Kirill Zhukov]

I’m a little confused by how to enable type resolution for commonMain source set? 🤔

[Kirill Zhukov]

Ah, looks like it’s simply not supported for common source set? https://kotlinlang.slack.com/archives/C88E12QH4/p1639596467112800?thread_ts=1639594663.111700&cid=C88E12QH4

[mkrussel]

I did some custom configuration and task building to make sure all the source sets being used by Android and JVM targets were added to the type resolution task instead of just their own. Then made sure I didn't create detekt tasks for the meta source sets.

My gradle expertise is not high, so there's probably a lot wrong with this script, but it seems to accomplish what I need.

Untitled.kt