Do not call FindReferencesAsync for null symbol #2089
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment, on finding references, when the requested symbol is null, we still call Roslyn reference finder API which then results in an ugly unhandled exception.
This happens automatically when the member is invalid and in VS Code shows up in a horrible way:
This also happens when you click anywhere in the code on a non-symbol e.g. the "public" keyword and try to use "find references"
Fixes dotnet/vscode-csharp#4382
Fixes #2054