gleam-lang/gleam

LSP module auto-import: handle module name collisions

Open

#3,269 opened on Jun 12, 2024

View on GitHub
 (0 comments) (0 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

Follows on from https://github.com/gleam-lang/gleam/pull/3219

It is possible for the LS autocompletion to add an import using a name that is already taken, causing a compile error.

How should we avoid this? Could we prompt the programmer for a name to use instead? Or do we generate a name?

Contributor guide

Research direction
Examine the current auto import implementation in PR #3219 and design a strategy to handle name collisions, such as prompting the user or generating a unique alias.
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.
Mostly clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45