gleam-lang/gleam

LSP: Support go-to-definition on record fields

Open

#5534 opened on Mar 29, 2026

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

Description

I'd like to be able to use go-to-definition with record fields

pub type Thing {
  Thing(a: String)
}

pub fn work() {
  let x = get_thing()
  x.a // go-to-def here!
}

I started working on this in #5533, with some Discussion in the Gleam Discord here

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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingGleam compiler internalsLSP protocol
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Examine the previous work in #5533 to understand the approach taken for go to definition on record fields. Review the Gleam compiler's AST representation for record fields in the type checking phase. Look at existing LSP handlers for go to definition in the codebase to see how other definitions are resolved. Implement the necessary logic to map field access to the field definition in the record type.