gleam-lang/gleam

LSP: sort complete suggestions after a pipe based on types

Open

#3,297 opened on Jun 19, 2024

View on GitHub
 (8 comments) (5 reactions) (0 assignees)Rust (960 forks)batch import
help wanted

Repository metrics

Stars
 (21,417 stars)
PR merge metrics
 (Avg merge 10d 19h) (69 merged PRs in 30d)

Description

I don't know how functional languages LSPs usually handle this case but it would be nice if suggestions after a pipe are functions that contain the type as the first parameter. i.e:

"hello" |> // <- This would only suggest functions that have String as the first parameter type

If there are multiple pipes, the suggestions should be related to the last output value.

"2" |> int.parse |>  // <- This would only suggest functions that have Result as the first parameter type

Contributor guide

Research direction
Investigate the current Gleam LSP completion system and understand how pipe suggestions are handled. Look into how other language servers (e.g., Rust Analyzer) implement type based filtering after pipes.
Tech stack
rust
Domain
developer experience
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.
1-2 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.
Clear
Prerequisites
GleamLSP concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40