gleam-lang/gleam

LSP Action: Move all imports to the head for the module

Open

#3,186 opened on May 24, 2024

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

Description

This would speed up adding modules while typing.

If there are multiple import groups it could be consistently added to either the head or tailed group.

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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
RustGleam compilerLSP basicsImport handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Review the existing LSP code actions in the Gleam compiler, particularly how imports are currently handled. Examine the AST representation of imports and determine the best location to insert new imports. Consider any maintainer comments for clarification on handling multiple import groups. Propose a consistent behavior and implement the code action in the LSP handler.
LSP Action: Move all imports to the head for the module · gleam-lang/gleam#3186 | Good First Issue