Skip to content

Work out how absolutizing paths should work #4278

Open
@michaelpj

Description

@michaelpj

Is your enhancement request related to a problem? Please describe.

We realised in #4231 that we don't really know how we are supposed to absolutise paths. We have a few cases:

  1. File paths that come from other tools, e.g. cabal. Probably these need to be relative to our working directory; or ideally we should avoid doing things that depend on our working directory at all.
  2. File paths that come from the client. Probably these need to be relative to a LSP workspace folder, but it's not entirely clear.
    • This is tricky: how do we know which workspace folder to use? Maybe we have to guess from the request? At least it would be nice to have whatever weird heuristic we end up with written down in some code.

It would be nice to tidy this up, but it probably relies on #4277 so we can actually tell where this is happening.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions