haskell/haskell-ide-engine

Completions should be import-aware

Open

#1,263 opened on May 21, 2019

View on GitHub
 (7 comments) (0 reactions) (1 assignee)Haskell (2,358 stars) (205 forks)batch import
good first issuetype: enhancement

Description

If adding a data type that takes a parameter to an import list, the snippet should be empty, and the completion should include (..) if it has subcomponents.

So

  , Foo

Should offer completion of FooBar(..), not FooBar Int or whatever.

Contributor guide

Tech stack
None
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.
clear
Prerequisites
Familiarity with Haskell module systemUnderstanding of IDE completion mechanisms
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Review the comments on issue #1263 for any discussion on implementation approaches. Examine the existing completion logic in the haskell ide engine codebase, particularly around import statements. Look at how the GHC API can be used to determine if a type has subcomponents (e.g., constructors, fields) that should be suggested with (..) syntax. Consider testing with a simple example like `import Data.Map (Map)` to see current behavior and expected output.