Support for AI Autocompletions via textDocument/inlineCompletion

Open
  • Is something wrong?
#4,965 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
vim
Domain
tooling

Research direction

No files or tests are named. Read the linked LSP 3.18 specification first, then locate ALE's existing LSP and completion entry points and their tests. Done means ALE can configure and handle textDocument/inlineCompletion consistently, with coverage for the new behavior.

Written by the indexing model from the issue text.

Description

enhancement

Huge fan of this project, and I've been using it since around 1.0 (nearly 10 year! time flies).

There's been a number of LSP projects that have recently adopted the textDocument/inlineCompletion method (part of the upcoming LSP standard here: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.18/specification/)

  1. Is it possible to configure this new method in ale currently?

  2. Is it possible to support this new method in a future release of ALE? (I'd be happy to take a swing at it, if pointed at the right direction).

Thanks!

Dominant language
Vim Script
Stars
14k
Forks
1.5k
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dense-analysis/ale

All issues in dense-analysis/ale

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.