parameter Hints in autocompletion preview - to show expected type of variable and other info

[blurymind]

1. The editor and gdscript are not consistent with the value type they take for rotations
   A hint about set_rot() type of expected variable would have helped me avoid a bit of confusion here:
   Ways Gdscript could be more user friendly and accessible  #4516 (comment)
   This is an example of how in some cases your code might parse successfully, but not do what you expect.
2. In order to know the type of variable that is expected in a function or a method, you need to search the class api documentation explicitly.
   In game maker, the auto - completion gives hints like this:
   
   So no need to search for this, the actual autocompletion is showing you immediately what type of value or syntax it expects!

Godot has no hints whatsoever.

To make this even more awesome than godot, gamemaker users can write hints for their own functions parameters. Defining a hint is as simple as:

http://gamemakerblog.com/2014/01/02/how-to-add-intelligent-code-completion-to-scripts/

This is a common feature of many other code editors.
Look at how nice it is in superpowers game engine:

This makes them easier to learn or transition to!

[akien-mga]

Well... Godot has autocompletion preview, I'm not sure what you're asking for.

[akien-mga]

[blurymind]

Actually I found out that another user has filed this last year:
#2378

this is the first thing. Autocompletion hinting is not very obvious. In other environments, the hints are shown in the results as you search. In godot you have to hit enter for the hint to appear. For that reason I wasnt getting the hints and realized it when another user on the issue tracker explained it.
Perhaps at least show the hint of the active selected item as you cycle through the results? Very often people dont hit enter at that precise moment.

The second thing is showing more information in the actual hint. set_rot () is a good example, because godot's hint does not tell the user that the value needs to be in radiants. Everywhere a radiant type float is expected - the hint should note that - so the user knows when it needs to be converted.
A bit more information as what it does would be nice too of course.

:)

But thats about it. I guess you can mark this as a duplicate of #2378

[neikeq]

I am not sure what exactly you are asking for, but it looks like a duplicate of #4370.

Well, that issue is about documentation generation. But the approach to document functions is the same as you would use for this.

[blurymind]

I guess I am asking for the function hints to also show up on autocompletion.
This:

Packs a lot more information than this:

The current way only shows hints once you settle for a function/method.
I guess it's not that bad as it is. Maybe I should close this feature request? We don't need it that badly

[Calinou]

This was implemented by #29744, closing.