-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add "Open Cargo.toml" action #6462
Comments
I can take this up if no one else is working on it. This would open the Cargo.toml of the current crate, right? |
Yes, but there might be some corner cases:
|
Right! i suggest looking at |
We just don't such features -- there's relatively few bugs on the interesection between client and server, and conventinal testing is not too efficient here. |
ah, got it 👍. What about manually verifying it works? Like installing a dev build and running that in vscode? |
@p3achyjr you can uninstall the store extension, run |
Invoking it should open Cargo.toml for the current file.
This should be implemented at the
rust-analyzer
layer (ie, not in the IDE layer).This needs custom protocol extension.
See c9f8789#diff-4bec6bfceb4323ffd0d2ff1ad25070234f084f31ddd5577bbdb510de878a3811 for an example which adds custom extension
The text was updated successfully, but these errors were encountered: