feat(completions): basic scoring algorithm for tables #150
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.
This PR tries to improve the existing
pg_completionscrate – autocompletions!The goal was to autocomplete table names based on the input:
select * from usshould put theuserstable before theemailstableselect * from private.ushould put theprivate.uncommonbefore thepublic.userstableAnd whoopdidoopdie, it works.
An overview of the changes:
Builder&Contextas well asCompletionItem+CompletionRelevanceto rank them (stolen fromrust-analyzer)tower_lsp::CompletionItemdata structuretower-lspversionREADME.mdto thepg_completionscrate