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
In the general case I can see why case-insensitive completion makes sense, but if I've explicitly provided an upper case letter I would expect it to prioritise exact matches.
What's even stranger is that without entering any text at all, Name is the first option:
The text was updated successfully, but these errors were encountered:
Thanks for the report. I think you're right: we should update our fuzzy matcher to prefer exact case match.
This is a gopls issue, so transferring to the gopls issue tracker.
findleyr
changed the title
Completion doesn't seem to prioritise explicit upper case matches
x/tools/gopls: prioritise explicit upper case matches in completion results
Nov 17, 2023
gopherbot
added
Tools
This label describes issues relating to any tools in the x/tools repository.
gopls
Issues related to the Go language server, gopls.
labels
Nov 17, 2023
There is a bonus for case sensitive match already here. I think the problem is we use the same bonus for matching the first letter of a segment, so the match bonus doesn't differentiate the case in this issue. It might work to just split those apart into separate bonuses.
In the general case I can see why case-insensitive completion makes sense, but if I've explicitly provided an upper case letter I would expect it to prioritise exact matches.
What's even stranger is that without entering any text at all,
Name
is the first option:The text was updated successfully, but these errors were encountered: