JuliaEditorSupport / JuliaEditorSupport/zed-julia

Migrate to JETLS language server

Open
#69 4 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
121
Forks
19
Avg merge
13h 44m
Merged PRs (30d)
7

Description

I'd like to start a discussion about migrating from LanguageServer to JETLS. I think it's safe to say that JETLS will eventually replace the old one everywhere—so, this issue is more about "when" we're migrating rather than "if".

We have several open issues regarding LanguageServer and we still don't have an update mechanism for it. As @aviatesk commented here:

Since JETLS itself can be installed as the jetls executable Pkg app as long as you have the julia binary and network access, implementing automatic installation might actually be easier than it is for LanguageServer.jl (and as an additional benefit of JETLS, complete isolation of the server's dependency environment is already implemented).

This alone would solve most of our headaches.

JETLS is currently only compatible with Julia 1.12.2–1.12.x. We don't know how many people are using zed-julia on Julia 1.10 LTS but as folks had to upgrade to LanguageServer 5.0.0 manually, we could just document the migration path or leave old installations as they are.

@aviatesk, what shall we do with Julia 1.13.0-rc1 and the upcoming release?

I’d appreciate any feedback, or just a thumbs-up if you agree.

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no files, tests, or entry points and is currently a migration discussion. First review the existing LanguageServer integration and JETLS compatibility across Julia versions, then establish an agreed migration path and acceptance criteria before implementation begins.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.