Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

The extended client capability: resolveAdditionalTextEditsSupport will be deprecated

Open
#430 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
emacs-lisp, java
Domain
tooling

Research direction

Start by locating extendedClientCapabilities and resolveAdditionalTextEditsSupport in lsp-java. Compare the current client capability handling with the linked JDT.LS and vscode-java changes. Done means the deprecated capability is no longer required while completion-item resolve support continues to work.

Written by the indexing model from the issue text.

Description

Since LSP 3.16, client can set resolveSupport to indicates which properties a client can resolve lazily on a completion item. JDT.LS will check resolveSupport to get which properties are supported in the completionItem/resolve request.

And that means there is no need to set resolveAdditionalTextEditsSupport in extendedClientCapabilities. resolveAdditionalTextEditsSupport will be deprecated.

More information, please check:

Dominant language
Emacs Lisp
Stars
696
Forks
97
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 emacs-lsp/lsp-java

All issues in emacs-lsp/lsp-java

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.