-
Notifications
You must be signed in to change notification settings - Fork 97
Use qualified module name from diagnostics in suggestNewImport #945
Conversation
Haven't looked at the code yet, but haskell/haskell-language-server#629 is about operators and the title of this PR "Use qualified module name in suggestNewImport" doesn't seem related. |
Ah, the issue was caused by we mistakenly stripped the qualified import prefix of identifiers. For example, if I write
The previous logic only took the first line, then tried to use But operators like |
Looks like the CI broke for some unknown reasons, but all checks passed on my fork: https://github.com/berberman/ghcide/tree/patch-qual |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, this is an awesome bug fix.
I don't know what the problem is with CI, could you perhaps rebase on top of master?
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
…ll/ghcide#945) * Use qualified module name from diagnostics in suggestNewImport * Update tests * Add newline * Use qualified module name from diagnostics in suggestNewImport * Update tests * Add newline * Remove unused renderImport Co-authored-by: Pepe Iborra <pepeiborra@gmail.com>
…ll/ghcide#945) * Use qualified module name from diagnostics in suggestNewImport * Update tests * Add newline * Use qualified module name from diagnostics in suggestNewImport * Update tests * Add newline * Remove unused renderImport Co-authored-by: Pepe Iborra <pepeiborra@gmail.com>
…ll/ghcide#945) * Use qualified module name from diagnostics in suggestNewImport * Update tests * Add newline * Use qualified module name from diagnostics in suggestNewImport * Update tests * Add newline * Remove unused renderImport Co-authored-by: Pepe Iborra <pepeiborra@gmail.com>
GHC helps us to split the qualified module name from the identifier. Closes haskell/haskell-language-server#629