-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Intellisense + Capital Letters #17275
Comments
Tag @kuhlenh @CyrusNajmabadi @rchande @DustinCampbell How do people feel about changing match preferences in cases like this? |
Basically, an exact case-sensitive, CamelCase match would beat out case-insensitive other matches. I think that's ok. If the filter text contains capital letters, that's a strong signal this is what the usre wants. I think we could safely take this. |
👍 ran into this today...wanted to do |
I"m also in favor of this. Sounds like a good tweak to me. |
I realized that name can also start with two upper-case letters (interface name). So I would say that priority should go like this:
|
Also see #16053 for discussion and the current behavior.
|
PLEASE make intellisense case-aware. Here's the kicker: When a user bothers to use the shift key to capitalize a letter, they want the variable or member that HAS that letter capitalized. |
@rchande , I have no idea how I managed "unassign" you above ... hopefully you can fix that, sorry. |
Version Used: Visual Studio 2017 RC 15.0.0-RC4+26206.0
Currently, when I type CR, a method with name C...R... is selected only if there is no method with name Cr...
I would propose that if I type CR and there is a method with name C...R..., it should take precedence over a method with name Cr...
The text was updated successfully, but these errors were encountered: