CHANGELOG

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog.

Note

JETLS uses date-based versioning (YYYY-MM-DD) rather than semantic versioning, as it is not registered in General due to environment isolation requirements.

Each dated section below corresponds to a release that can be installed via Pkg.Apps.add(; url="https://github.com/aviatesk/JETLS.jl", rev="YYYY-MM-DD")

To install the latest version regardless of date, re-run the installation command:

julia -e 'using Pkg; Pkg.Apps.add(; url="https://github.com/aviatesk/JETLS.jl", rev="release")'

Unreleased

Commit: HEAD
Diff: 72cc49c...HEAD

Announcement

Important

JETLS requires Julia 1.12.2 or later. It does not support Julia 1.12.1 or earlier, nor Julia 1.13+/nightly.

Warning

JETLS currently has a known memory leak issue where memory usage grows with each re-analysis (aviatesk/JETLS.jl#357). As a temporary workaround, you can disable full-analysis for specific files using the analysis_overrides initialization option:

// VSCode settings.json example
{
  "jetls-client.initializationOptions": {
    "analysis_overrides": [
      { "path": "src/**/*.jl" },
      { "path": "test/**/*.jl" }
    ]
  }
}

This disables analysis for matched files. Basic features like completion still might work, but most LSP features will be unfunctional. Note that analysis_overrides is provided as a temporary workaround and may be removed or changed at any time. A proper fix is being worked on.

Warning

The inlay_hint configuration was reorganized into nested sub-tables so each hint kind has its own enabled toggle alongside its options. The new shape adds inlay_hint.block_end.enabled for toggling block-end hints independently, and renames inlay_hint.block_end_min_lines to inlay_hint.block_end.min_lines. Existing configs keep working for now: the legacy key is still accepted at load time and mapped onto the new key in memory (your config file is not modified automatically), with a one-shot deprecation warning. The legacy alias will be removed in releases after June 2026, so if you are still using inlay_hint.block_end_min_lines, please update your config.

Warning

The completion.method_signature.prepend_inference_result configuration option was removed. Inferred return types are now always shown both as CompletionItem.detail (-> T typically shown next to the candidate label) and as a leading signature -> T code fence at the top of the method signature completion documentation, so the previous client-specific opt-in is no longer needed. Existing configs keep working for now: the removed key is still accepted at load time and silently dropped, with a one-shot deprecation warning. The legacy key will be rejected outright in releases after June 2026, so if you are still setting completion.method_signature.prepend_inference_result, please remove it from your config.

Added

Added support for "Go to Type Definition" (textDocument/typeDefinition). Invoking it on an expression jumps to the definition of its inferred type — e.g. landing on a binding of type Foo jumps to the struct Foo definition. For Union types the response includes one location per constituent. (aviatesk/JETLS.jl#686)

Added property completion (x.│ / x.partial│). Typing . after a typed expression now offers the properties that propertynames(::T) reports for the dot prefix's inferred type — both plain struct fields and types with a custom propertynames overload are handled uniformly. Each candidate's inferred property type (x.field :: T) is resolved lazily, only when the client requests details for a focused item. For union-typed prefixes the offered names are the union of each component's propertynames, so the common Union{T, Nothing} pattern still surfaces T's properties even though propertynames(::Nothing) == (); type details merge each component's per-property type at resolve time.

Changed

textDocument/hover now surfaces inferred types alongside documentation. Any identifier, dot expression, call result, or indexing position can be queried — func(x) :: Int, s[2] :: Float64, Base.Pair :: typeof(Pair), etc. — and the type is queried at the cursor's byte range so flow-sensitive type narrowing is reflected. Binding hovers additionally carry a kind tag — (argument), (local), (static parameter), or (global) — before the name, making the binding's role in scope visible. Closures display as function-arrow signatures like (x::Int, y::Int) -> Int, with argument names recovered from the body when available. Documentation is gathered both from the binding's own docstring and from the docstring of whatever value the expression resolves to via type inference. So e.g. given sv = Some(sin), hovering on sv.value shows sin's docstring even though sin doesn't appear at the cursor. When the cursor is on the callee identifier (e.g. sin│(rand(Int)), Base.Math.sin│(x)), the header is promoted to the full call expression (sin(rand(Int)) :: Float64) and the docstring is narrowed to the dispatched method's doc when dispatch resolves to a single method (sin(::Real)). When the cursor sits past a call-like surface's closing punctuation (f(args)│, xs[i]│, [a, b]│, …), only the expr :: T header is shown without any docstring body. Non-call cursors (f│) still show every overload's doc. (aviatesk/JETLS.jl#687)

Hover on call	<img width="1086" height="418" alt="Hover on call demo" src="https://github.com/user-attachments/assets/cf3d2eb8-3036-44e2-b075-b3c9ca09dc35" />
Hover on closure	<img width="1086" height="418" alt="Hover on closure demo" src="https://github.com/user-attachments/assets/285de208-a704-4978-9a89-829654f561bc" />

textDocument/definition on a call site (f(arg)│ or f│(arg)) now narrows to the method dispatch picked for the inferred argument types — e.g. sin│(42) jumps to sin(::Real) only, not to every method of sin. Bare cursors on the function name (sin│) still return all definitions.
textDocument/signatureHelp and method-signature completion (textDocument/completion) now narrow overloads using the inferred type of each argument at the call site, including arbitrary local-scope expressions. Previously only top-level globals and literal arguments contributed to filtering, so let x = rand(); sin(x,│); end showed every sin method; with the local x :: Float64 now folded in, only sin(::T) where T<:Union{Float32, Float64} is offered.
textDocument/semanticTokens now classifies type parameters declared in struct / abstract type / primitive type headers (and their use sites inside the type body) as typeParameter. Previously these identifiers were classified as plain variable.
lowering/undef-global-var now suppresses reports as soon as a sibling file in the same analysis unit defines the referenced name. Previously, adding foo = ... to one file left foo references in other files of the same unit flagged as undefined until the next full-analysis cycle (typically triggered on save) caught up.
lowering/macro-expansion-error no longer aborts analysis of the enclosing top-level form. Any misuse JETLS's stubs for Base macros detect — invalid threadpool literal in Threads.@spawn, duplicate kwarg in @info/@warn/…, @test with skip + broken, wrong argument count in @assert/@invoke/@kwdef/@assume_effects/…, non-call shape passed to @invoke, malformed @testset body, and so on — is now reported in place while the macrocall body still flows through to scope and type analysis. Previously any of these would propagate a MacroExpansionError, remove the entire macrocall from analysis, and take every other LSP feature requiring full lowering of the enclosing function (hover, inlay, signature help, undef-var, references, …) down with it. Reports come with Error severity when Base would reject the misuse and Warning severity when Base accepts it silently or only deprecates.
Documenter admonitions (!!! note, !!! tip, !!! warning, !!! danger, !!! info, !!! compat) in docstrings now render as Markdown blockquotes with a category-emoji header (e.g. > **💡 Tip**) wherever JETLS surfaces docstrings (hover, completion documentation, signature help). Previously the !!! block leaked through verbatim, leaving the editor's Markdown view to render it in unintended ways.
Hover and method-signature completion documentation no longer surface Base's "No documentation found for ..." placeholder paragraph for bindings that exist but carry no docstring. The auto-generated method / type summary that follows the placeholder is still shown, so the hover stays informative without the placeholder noise.