You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if i'm understanding the situation correctly (after skimming through microsoft/vscode#94637), it seems that SignatureInformation.activeParameter is supposed to replace the top-level one in textDocument/signatureHelp. but currently there are two of them and the documentation doesn't really explain why. in fact the documentation on the top level one seems to imply the opposite, since it says the following:
In future version of the protocol this property might become mandatory to better express the active parameter if the active signature does have any.
i think either the top-level one should be explicitly marked as deprecated, or the documentation should be updated to clarify which one is preferred.
The text was updated successfully, but these errors were encountered:
if i'm understanding the situation correctly (after skimming through microsoft/vscode#94637), it seems that
SignatureInformation.activeParameter
is supposed to replace the top-level one intextDocument/signatureHelp
. but currently there are two of them and the documentation doesn't really explain why. in fact the documentation on the top level one seems to imply the opposite, since it says the following:i think either the top-level one should be explicitly marked as deprecated, or the documentation should be updated to clarify which one is preferred.
The text was updated successfully, but these errors were encountered: