Update default for "editor.suggestSelection" to "first", fixes #86. #94
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.
Previously, the default "editor.suggestSelection" value was "last"
causing VS Code to pre-select counter-intuitive completions items.
For example, if you selected
toString()
once, then VS Code wouldpre-select
toString()
in the following completion regardless of theorder of completions returned by Metals.
Metals already orders completion items in a "smart" order based on the
local scope and completion position (pattern matching vs. type vs.
term). Now with this change, VS Code always pre-selects the first
completion item returned by Metals.