Skip to content

Gleam LSP don't show my new module in LSP actions #5371

@gungun974

Description

@gungun974

Okay I really like Gleam as a language but sometimes I just want to hate it's LSP when it come to do refactoring 😅
Often I have a type with some functions I need to make them common for multiple module so what I want to do is move this code to a new file than in the original file replace the function and types with imports.

My issue is while doing this my LSP is kind of dead and refuse to auto import my new module if I don't have an import.
I made three videos:

gleam --version
gleam 1.14.0

I don't have logs for the Gleam LSP but I think it's easily reproducible with my videos linked above.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions