gleam-lang/gleam

Support workspace symbols in language server

Open

#5191 opened on Dec 7, 2025

View on GitHub
 (8 comments) (1 reaction) (0 assignees)Rust (21,417 stars) (960 forks)batch import
help wanted

Description

Would be nice to be able to navigate to types and functions across the whole workspace: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_symbol

I had a brief look at the code and the immediate hurdle seems to be the routing within the language server. For document-level requests we determine the project to operate on from the document's file path. For workspace requests this path is simply not present.

I'd be happy to work on this if we can find a way around that!

Contributor guide

Tech stack
rust
Domain
developer experiencetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Rust programmingLSP protocol basicsFamiliarity with Gleam codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Investigate the current language server routing code to understand how project context is determined from document paths. Look for alternative ways to infer the project for workspace level requests, possibly by scanning the workspace folder. Consult the language server specification for workspace/symbol and consider using the existing document symbol code as a starting point.