feat: rank and sort completions server-side by relevance#143
Merged
Conversation
Completion items now carry a zero-padded `sort_text` derived from a relevance key (match quality, then scope proximity, then length/label). A case-matching prefix ranks above a case-insensitive one, so an all-lowercase query surfaces the lowercase symbol first (e.g. `\epsi` suggests `\epsilon` before `\Epsilon` without dropping the latter), and bindings in nearer lexical scopes come first. Editors that don't sort completions client-side now get a sensible order too. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Completion items now carry a zero-padded
sort_textderived from a relevance key (match quality, then scope proximity, then length/label). A case-matching prefix ranks above a case-insensitive one, so an all-lowercase query surfaces the lowercase symbol first (e.g.\epsisuggests\epsilonbefore\Epsilonwithout dropping the latter), and bindings in nearer lexical scopes come first. Editors that don't sort completions client-side now get a sensible order too.Fixes julia-vscode/LanguageServer.jl#1384.