[danusha2345]

Summary

#2196 made a Kotlin import from outside the project own its name: after import androidx.compose.ui.Modifier, Modifier.fillMaxSize() no longer lands on a same-named project method. That rule returns before every other strategy, so a project extension declared on the imported type can't be reached either:

// ui/Ext.kt                              // ui/Screen.kt
package app.ui                            package app.ui
import androidx.compose.ui.Modifier       import androidx.compose.ui.Modifier
fun Modifier.pad(): Modifier = this       fun screen() { Modifier.pad() }   // no edge

(Before #2196 this call was already dropped by the "receiver names a type the project doesn't declare" guard in matchMethodCall; #2196 adds a second block in front of every strategy, so it can no longer be fixed there.)

Change

Inside the outside-import rule, a Kotlin Type.member call now resolves to a project extension indexed as Type::member when

• the call site can see it — same file or package, or imported by name or .* (the existing isKotlinTopLevelVisible / kotlinFileScope), and
• the extension's own file imports the same outside type (so an extension on javax.lang.model.element.Modifier is not Compose's).

If several qualify, only one in the calling file is taken; otherwise no edge. Everything else stays unlinked as before — Modifier.fillMaxSize() included. Color.fromHex() on a fun Color.Companion.fromHex() is covered the same way. Chains through an outside call (Modifier.fillMaxSize().pad()) are untouched: the outside call's return type is unknown, and they did not resolve before #2196 either. An instance receiver (val m: Modifier; m.pad()) already resolved on main and is unaffected.

Tests

__tests__/kotlin-extension-on-imported-type.test.ts (fails on main, passes here, kernel and wasm extraction): same-package call, imported-by-name and .* calls, an unimported extension (no edge), an extension on a different Modifier type (no edge), and Compose's own member (no edge). Dropping either check yields a wrong edge in the test. Full suite on Linux passes; the Kotlin suites and #2196's java-outside-imports.test.ts pass with CODEGRAPH_KERNEL_EXPECT=1.

Measurements

Three Android apps (132–793 JVM files): edges identical before and after (0 added / 0 removed) — they call their own extensions through instances only, which #2196 never blocked. So this is a precision-safe fix for the Type.extension() shape rather than a measured win on these repos.

The visibility check follows the kotlinExtensionInScope idea from @mixxer's #1948 discussion; thanks!

🤖 Generated with Claude Code

[colbymchenry]

Thanks @danusha2345! This landed in #3011, with you as the commit author. Calls like Modifier.secondaryItemAlpha() now reach the project's own Compose extensions: 28 new links across mihon and nowinandroid in our A/B, with nothing lost, and it works alongside the Kotlin receiver typing from #1933. We only moved the CHANGELOG entry next to the other Kotlin ones.