Godot code completion not showing available signal when calling connect() on node reference

[ryanalbrecht]

Godot code completion not showing available signal when calling connect() on node reference

[KoBeWi]

It's not only new, it's better. You don't use strings but actual signal references, so it's safer.

[KoBeWi]

Why aren't you using the new syntax, i.e. $Area2D.custom_signal.connect()? The signals should be properly suggested this way.

[ryanalbrecht]

@KoBeWi no particular reason. I am very new to Godot and I was following a tutorial and went down a rabbit hole to and figure out what was wrong with the editor and discovered this bug and thought I would report it.

On the subject of the new syntax I did start using this in favor of the old, however I do find the old syntax with the popup very useful to show exactly what signals are available. At first the engine is difficult to get your mind around and this helps.

[JekSun97]

$Area2D.custom_signal.connect()? The signals should be properly suggested this way.

Just because it's new doesn't mean you have to use it :)
I'm used to the old syntax and don't regret it

[HolonProduction]

Very likely another regression from #79386 which might be somewhat similar to #92219, in that the value does not end up in the final type.

Even though there is a better way for signal connection, this should be fixed, as it might turn up with other argument options like AnimationPlayer.play

Note to my self: extend the autocompletion tests to incorporate argument options on get_node