For the following example case, in KSP2 I'm finding that the KSType representing it has its arguments from the aliased type attached, when I would expect (and what I believe happens in KSP1) these arguments to only be on the aliased type
typealias BaseEmbedViewBinder = ViewBinder<out BaseViewHolder, out SpaceshipEmbedModel>
private val viewBinderProviders:
Map<Class<out BaseViewHolder>, @JvmSuppressWildcards Provider<BaseEmbedViewBinder>>,
In this case, the KSType representing Provider<BaseEmbedViewBinder> is actually being represented as a KSTypeAlias with declaration BaseEmbedViewBinder and two type arguments <out BaseViewHolder, out SpaceshipEmbedModel>

For the following example case, in KSP2 I'm finding that the KSType representing it has its arguments from the aliased type attached, when I would expect (and what I believe happens in KSP1) these arguments to only be on the aliased type
In this case, the
KSTyperepresentingProvider<BaseEmbedViewBinder>is actually being represented as a KSTypeAlias with declarationBaseEmbedViewBinderand two type arguments<out BaseViewHolder, out SpaceshipEmbedModel>