Skip to content

Support multi-root workspaces #24

@davidovich

Description

@davidovich

Problem

When you use multiple folders in a VSCode workspace, the jpath is constructed with first workspace folder.

I have many jsonnet folders that respect a general hierearchy, and they are all in a named workspace.

# foreach folder of the workspace

     vendor/ # as produced by jsonnet bundler
     lib/ # local libraries
     build/ # some generated json files for import 

I set my jpath to [vendor, lib, build], but my libsonnet files are still not found, if I am not in the first folder.

Browsing through the code, I see that only the first project is used to deduce an absolute jpath. Also, this seems to happen on start of client, and on config reload. This seems like a global setting sent to the language server...

Expectation

I would expect hat the configured jpath is relative to the current folder of the current workspace and that the extension use the current context to find my files.

Notes

Maybe we could use the asRelativePath function of the workspace API, or getWorkspaceFolder to deduce the correct jpaths.

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