-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reload workspace when cargo.toml is changed from outside(e.g. cargo add
)
#423
Comments
Hey 👋 This is out of scope for rustaceanvim and would need to be implemented in rust-analyzer. |
I'm curious why VSCode can have it reloaded automatically. |
It does? |
Yes, I can show you: vscode.mp4 |
If the file watcher is registered as the client (which should be the default) it is the client's job to inform the server of any relevant file changes. |
This should probably be implemented via the As I said, this is likely out of scope for rustaceanvim, so I will have to put some thought into it. |
In that case you could probably hardcode the |
Perhaps it makes sense to check if the neovim has the client capability and hardcode the config if it doesn't. That way we don't risk running into problems if neovim enables the capability again. |
Feature description
Now when I add a crate via
cargo add
, I need to manually open thecargo.toml
and:w
to force reloading the workspace.It is better to watch the
cargo.toml
and reload no matter how it changed.The text was updated successfully, but these errors were encountered: