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
Actual behavior: Note: there are also methods in this list. However, amount of delegates is larger, so methods items need some scroll to be seen
Additional context:
In C# the behaviour is expected:
And also in C# there are different categories for methods and delegates:
Also note inconsistency in UI: in C# there are more categories in general, they are sorted differently, and there is a green "plus" icon for showing advanced members, I believe. And when I select some category in C# all other icons fade out, while in razor they do not.
The behaviour of razor should fully match the behaviour of C# here IMO
The text was updated successfully, but these errors were encountered:
ghost
added
the
untriaged
Issues and PRs which have not yet been triaged by a lead
label
Apr 14, 2022
davidwengier
changed the title
Filtering completion items for methods also filters delegates
[LSP] Filtering completion items for methods also filters delegates
Apr 14, 2022
jinujoseph
added
Bug
LSP
issues related to the roslyn language server protocol implementation
and removed
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Apr 19, 2022
Version used:
VS 2022 v17.2 Preview 3
To reproduce:
.razor
fileExpected behavior:
I see only available methods
Actual behavior:

Note: there are also methods in this list. However, amount of delegates is larger, so methods items need some scroll to be seen
Additional context:

In C# the behaviour is expected:
And also in C# there are different categories for methods and delegates:

Also note inconsistency in UI: in C# there are more categories in general, they are sorted differently, and there is a green "plus" icon for showing advanced members, I believe. And when I select some category in C# all other icons fade out, while in razor they do not.
The behaviour of razor should fully match the behaviour of C# here IMO
The text was updated successfully, but these errors were encountered: