Could you provide an example usage of this new method?

Could you provide an example usage of this new method?

@syntaxerror247 I've updated the description with code examples.

• Add overload method for GodotPlugin#emitSignal(...) that takes in a SignalInfo argument.
  It's common for GodotPlugin implementations to define a set of SignalInfo objects to use for registration, then reuse those objects when a signal is emitted. This typically looks like:

private val EVENT_SIGNAL = SignalInfo("event_signal")
...
override fun getPluginSignals() = setOf(EVENT_SIGNAL)
...
fun dispatchEvent() {
    emitSignal(EVENT_SIGNAL.name)
}

With this update, the call to emit the signal can be changed to:

fun dispatchEvent() {
    emitSignal(EVENT_SIGNAL)
}

Hm.. I don't see any use for this overloaded method because you can create string constants for signal names. Eg.

private val EVENT_SIGNAL = "event_signal"
override fun getPluginSignals() = setOf(SignalInfo(EVENT_SIGNAL))
fun dispatchEvent() {
    emitSignal(EVENT_SIGNAL)
}

Since you’re working on this, would it be possible to support nullable parameters?
For ex, I have the following method in my plugin:

@UsedByGodot
fun testMethod(param1: String?) {
    if (param1 != null) {
        Log.d("godot-test", param1)
    } else {
        Log.d("godot-test", "param1 is null")
    }
}

when I call plugin_singleton.testMethod(null) from gdscript, it throws an error saying the function doesn’t exist, since it only accepts a string.

Since you’re working on this, would it be possible to support nullable parameters?
For ex, I have the following method in my plugin:

@UsedByGodot
fun testMethod(param1: String?) {
    if (param1 != null) {
        Log.d("godot-test", param1)
    } else {
        Log.d("godot-test", "param1 is null")
    }
}

when I call plugin_singleton.testMethod(null) from gdscript, it throws an error saying the function doesn’t exist, since it only accepts a string.

Yeah I can take a look!

Since you’re working on this, would it be possible to support nullable parameters? For ex, I have the following method in my plugin:

@UsedByGodot
fun testMethod(param1: String?) {
    if (param1 != null) {
        Log.d("godot-test", param1)
    } else {
        Log.d("godot-test", "param1 is null")
    }
}

when I call plugin_singleton.testMethod(null) from gdscript, it throws an error saying the function doesn’t exist, since it only accepts a string.

@syntaxerror247 I thought on it some more, and I think it's better to keep the current limitation in place for a few reasons:

• It aligns with gdscript type system. The limitation you mention only applies to String and Callable which matches gdscript static typing when it's enabled. E.g: A String variable in gdscript cannot be assigned null when static typing is enabled.
• Removing this limitation would be fine when interacting with Java code, but would be an issue when interacting with Kotlin code. From the gdscript side, we can't tell when a String argument to a Kotlin method is a nullable String or a non-nullable String. As such the safe approach is to assume that it's a non-nullable String and prevent passing null because the developer has control over the gdscript code and can modify it to accommodate the limitation (e.g: passing an empty string instead), whereas the Kotlin side can be a third-party library that's unable to be modified, where passing a null value could cause a runtime NullPointerException.
• Last, as Kotlin and gdscript demonstrate, pushing for null-safety is a safer, more robust approach to development, so we should encourage that approach whenever possible (e.g: passing empty string instead of null values).

Thanks!