[Call for testing] Experimental signature help support in the editor tooling

Development
1

The latest VSCode extension pre-release has experimental support for signature help. For those who don’t know, signature help is the small window that pops up as you’re writing a function call, telling you about the various parameters of the function.

Our experimental version looks like this:

image
image1196×146 9.87 KB

With no parameter active

image
image1342×606 55.6 KB

With an active parameter

We’re interested in hearing your feedback on this feature. You can activate it by changing the setting Rescript > Settings > Signature Help: Enable to true.

Looking forward to hearing your thoughts!

21 Likes
2

Thank you very much for this feature. I’m on the pre-release channel.

Function signature is not displayed when opening parentheses (.

Example:

let add = (~x, ~y) => x + y
add(

config:

"rescript.settings.signatureHelp.enable": true,
3

This feature will make our life much easier. Thank you!

2 Likes
4

Has that function compiled? The function must have compiled at some point.

5

Feature feels great. Great job creating pragmatic, useful dev tooling for the community :slight_smile:

1 Like
6

I had this setting enabled. Now it’s working. :grinning:

"editor.parameterHints.enabled": false,
7

The parameter is highlighted after insertion, shouldn’t it be highlighted after triggering the characters (, , and =?

image

image

image

The function name let add: is redundant could we just show the signature like codelens does?

Example:
(int, int) => int

1 Like
8

@aspeddro both of those points are now fixed in the pre-release version.

1 Like