In 2.0.0 I'm seeing behavior like <https://github.com/google/ksp/issues/1849> where if there's a typ...

# ksp

[eygraber]

In 2.0.0 I'm seeing behavior like https://github.com/google/ksp/issues/1849 where if there's a typealias in the module that I'm running KSP on, it is a KSTypeAlias but if it is in another module then it is the resolved type.

Is this expected or a bug?

[Jiaxiang]

it might be a limitation from upstream analysis API, I will take a look and sync with JB if necessary.

[eygraber]

thank you color

I'm working on putting together a MRE

[eygraber]

Actually looks like it's related to the Compose compiler being in the project.

[eygraber]

The issue is if the typealias is a @Composable function, and that function lives in a different module than the one that KSP is running in. It happens with KSP1 and KSP2. I'll open a new issue because I'm not sure if it's related to the one I linked above.

[eygraber]

Filed https://github.com/google/ksp/issues/1921

[eygraber]

@Jiaxiang is it possible that this is something on the Compose compiler's side? Should I file something there as well?

[Jiaxiang]

I think it is a known issue on KSP side.

[eygraber]

Something fixable, or it requires compiler changes?

[Jiaxiang]

I will investigate it.

[eygraber]

@Jiaxiang any update?