Skip to content

No support for workspaces (aka monorepo) #42

Description

@luc-j-bourhis

My situation is a Project.toml in a top directory like:

[workspace]
projects = ["PackageA", "PackageB", ...]

[deps]
PackageA = "..."
PackageB = "..."
...

and then "PackageA/Project.toml", "PackageB/Project.toml", … are just of the vanilla kind. This will result in a single "Manifest.toml" in the top directory, that merges the dependencies of all the dependencies listed in "PackageA/Project.toml", "PackageB/Project.toml", …

But then, when I open a source file inside "PackageA" that features using FileIO for example, hovering over "FileIO" does not show anything, and I don't get any completion of the symbols exported by FileIO either (e.g. File, format, etc). Apart from that, LSP works superbly in my SublimeText. Is that actually a limitation of the LSP server itself? Or is there a configuration tweak I am missing? The only configuration I touched is User/LSP-julia.sublime-settings:

{
    "julia_executable_path": "/Users/luc/.juliaup/bin/julia",
    "julia.lint.missingrefs": "all",
    "enabled": true,
}

I tried to use the command LSP-Julia: Change Current Environment: it finds the top directory but selecting that does not solve my problem.

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