-
Notifications
You must be signed in to change notification settings - Fork 671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No IntelliSense & parameter hints for calls to local functions #1715
Comments
This is another good one for @akshita31 to look at (cc @DustinCampbell @TheRealPiotrP ) |
Agreed. @akshita31, I went ahead and assigned this to you. |
The problem here is that in the SignatureHelpService, we are first finding the containingType for the given invocation and then returning all the methods in that containingType with the same name as the method. In case of localFunction , the containing type is being returned as the Class name and not the main function .But I am not sure whether this is the problem with roslyn returning the incorrect containingType or a problem with the way we are finding the methodOverloads in omnisharp-roslyn. |
The fix for this issue has been merged into OmniSharp. Once we take a new build of OmniSharp, it will appear here. |
This issue has been fixed in the 1.14 milestone. We just released a beta of 1.14 - https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.14.0-beta4. Follow these instructions to install a beta release of C# for VS Code. |
Environment data
dotnet --info
output:VS Code version:
1.14.2
C# Extension version:
1.11.0
Steps to reproduce
Create a local function, and make a call to it:
Expected behavior
When typing arguments for the call to the local function, in
var flag = LocalFunction(1);
, IntelliSense should be provided for the parameter hints.When using the feature
Trigger Parameter Hints
⇧⌘Space it should trigger the parameter hints for the call to the local function.Actual behavior
No IntelliSense provided for 1, and no parameter hints triggered for 2.
The text was updated successfully, but these errors were encountered: