[LSP Spec]: In response of signatureHelp, activeSignature starts from 1

[jinzhongjia]

I recently discovered a problem when using basedpyright on neovim
But this problem should not require code to reproduce. You only need to find a python method with parameters to verify it.

main

https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#signatureHelp

According to doc, activeSignature should start from 0, but now it is start from 1

I'm not sure if this is really a problem, so I'll ask and if there is no problem please close the issue.

[jinzhongjia]

I tested it further and found that the signaturehelp of list.sort() is incorrect. It starts from 1
But the signaturehelp of print() is correct, it starts from 0

This behavior is strange

[KotlinIsland]

is activeSignature related to overloads?

could you please provide steps on how to reproduce this? something like:

1. enter

   print()
   list.sort()

2. check language server logs for signatureHelp response

[DetachHead]

yeah i don't really understand what signatureHelp is and the language server documentation doesn't have any screenshots so i will need some more information. preferably a screenshot of what exactly is incorrect with list.sort() compared to print()

[jinzhongjia]

I will try to check the logs later

[KotlinIsland]

when you say that it "starts from 1", what exactly do you mean? how do you know that it is starting from 1? where you can see this information?