LSP has no way to indicating to the server that the active signature has been changed on the client.

[tinaschrepfer]

• User invoke signature help on VS Code (or any client support LSP) and there are multiple matching signatures.
• User selects a different signature on the client and then starts typing parameter

Expected:
The selected active signature should not change.

Actual:
The selected active signature changes to the first one.

This occurs because there is no mechanism in the LSP for the client to send a message to the server that the active signature has changed.

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Add context information to SignatureHelpProvider (#54972)
• Client should report current value of activeSignature to signatureHelpProvider (#33413)

[dbaeumer]

@jrieken I looked at the code and this seems to be a problem already with the VS Code API. I couldn't find a way how we would tell the signature help provider that the user actually has chosen the second signature.

I tested this with TS and it always falls back to the first signature that matches the types parameters regardless which one I selected before.

Anything I am missing?

[jrieken]

yes - this is #33413

[dbaeumer]

Closing as dup then #33413