gleam-lang/gleam

LSP: Support triggering find references from imports

Open

#5544 opened on Mar 31, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (21,417 stars) (960 forks)batch import
help wanted

Description

In the following example, triggering find references on any of the underlined locations should show all of the uses of the type Foo. It currently works everywhere but in the import line.

// -- foo.gleam
pub type Foo
//       ^^^

// -- app.gleam
import foo.{type Foo}
//               ^^^ ← this line shows up in all results, but triggering here fails
fn main() {
  let _: Foo = todo
  //     ^^^
}

Contributor guide

Tech stack
rust
Domain
backenddeveloper experiencetooling
Issue type
bug
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingLSP basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Look at the find references handler in the LSP implementation, likely in `compiler core/src/language server/`. The current behavior returns results for import lines but does not trigger from them. Investigate how the import token is resolved and ensure it returns the same reference locations as other usages.