-
Notifications
You must be signed in to change notification settings - Fork 164
support for opening a parent directory of the rust project #507
Comments
This bit looks like the culprit: https://github.com/rust-lang/rls-vscode/blob/f23a1d54c47b2f9e7595bca8c66f30d4abeba357/src/extension.ts#L60 |
Having the same issue, kind of annoying :( |
yea just ran into this as well, can work around it but this particular issue does make working with mono-repo style projects less than ideal. |
A pull request solving this issue is open here #638 ! |
FWIW this works out of the box with rust-analyzer. |
@samuela I am not sure it does, I am currently running on Windows with Rust-client Engine set to rust-analyzer in my user settings and it only works for me when my root directory is the rust project folder |
Further testing it looks to only go one parent folder deep. My folder structure looks more like this:
when in my-project wasm-crate does not get completion. Although I guess quick fix would be to rearrange like this:
then just use a relative path from webpack-frontend to wasm-crate. Sorry I am just doing stream of conscious, if someone else comes across my same case could be useful. |
I have a project laid out as a monorepo, something like:
Now rls-vscode works great if I open up vscode at
my-project/rust-project/
but it doesn't work at all if I open up the root foldermy-project/
as I prefer to do:It would be nice to support project lookup relative to the file actually being edited as opposed to just assuming that the whole folder is a rust project. Because monorepos, blah blah blah.
The text was updated successfully, but these errors were encountered: