Type aliases aren't unwrapped when processing property, function, and signal registrations

[marcopennekamp]

I'm trying to define type aliases for primitives and Godot types, but I'm running into issues with registered properties/functions/signals.

Version: 0.11.0-4.3

Property Registration

I have the following type alias:

typealias SchemaId = String

I'm trying to register a property with this type:

@Export
@RegisterProperty
var schemaId: SchemaId = ""

But this leads to the following exception during compilation (from KSP):

[ksp] <path>: Registered property can only be of type primitive, core type, node type or ref counted

Expected behavior: The registration processor recognizes that the SchemaId type is actually a String type.

Function Registration

I have the following type alias:

typealias GlobalPosition = Vector2

I'm trying to register the following function:

@RegisterFunction
fun changeZone(destinationScene: PackedScene, destinationPosition: GlobalPosition) {
    // ...
}

Unfortunately, this leads to the following registration in the class's registrar:

function(MyGame::changeZone, NIL, OBJECT, GLOBALPOSITION, KtFunctionArgument(OBJECT, "godot.PackedScene", "destinationScene"), KtFunctionArgument(GLOBALPOSITION, "mygame.core.GlobalPosition", "destinationPosition"), KtFunctionArgument(NIL, "kotlin.Unit"), KtRpcConfig(RPC_MODE_DISABLED.id.toInt(), false, TRANSFER_MODE_RELIABLE.id.toInt(), 0))

The generated code cannot be compiled because GLOBALPOSITION doesn't exist.

Expected behavior: The registration processor recognizes that GlobalPosition is a Vector2 and uses this type in the registrar.

Signal Registration

Taking the same GlobalPosition type alias, I'm trying to declare the following signal:

@RegisterSignal
val changeZone by signal2<PackedScene, GlobalPosition>("destinationScene", "destinationGlobalPosition")

This results in the following registrar code:

signal(GlobalSignals::changeZone, KtFunctionArgument(OBJECT, "godot.PackedScene", "destinationScene"), KtFunctionArgument(GLOBALPOSITION, "mygame.core.GlobalPosition", "destinationGlobalPosition"))

This again fails to compile because GLOBALPOSITION doesn't exist.

[CedNaru]

That issue will probably be resolved automatically by #761.
TypeAliases probably appear as their original class in bytecode so you will get the behavior you want.

[marcopennekamp]

Nice, yup, usages of type aliases are expanded in the bytecode. Thanks for the quick response!

[chippmann]

Still I think once that's merged, we should add some tests for these cases.