-
Notifications
You must be signed in to change notification settings - Fork 2.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
rust-analyzer fill matching arms does not work in theia but works in vscode #13922
Comments
Thank you for the report. Could you paste a link to the to extensions on openVSX and ideally also the versions of the extensions you are using? |
Thanks, you also mention "Cargo" needs to be installed, could you provide the details there, too? |
Cargo comes with Rust(which is what is also needed): |
@hsnoil what version of TheiaIDE are you using? |
@tsmaeder In the initial post they mention:
|
I think I may have narrowed down the problem. The issue is likely related to doing a set of a SnippetTextEdit This is the part where it fails:
https://github.com/rust-lang/rust-analyzer/blob/master/editors/code/src/snippets.ts on vscode the applyEdit returns true, while Theia returns false. Doing a few tests, if I use a TextEdit, it works (but then you lose templates of the SnippetTextEdit) Edit: |
I notice there are some differences for set between theia and vscode. Not sure if that is the issue as the pc I am on is has too little space which won't let me compile Theia:
As you can see, edit should be equal to edit.snippet but it ends up as edit: { snippet: edit.snippet } |
Bug Description:
When using rust-analyzer extension, the fill match arms does not work on TheiaIDE appimage, but it works fine on vscode. Other rewrites work, just not fill match arms
Steps to Reproduce:
cargo new test1
src/main.rs
:match pet {
line should highlight as an error, mouse over it and scroll down to Quick fix... orctrl+.
and click onFill match arms
, nothing happensAdditional Information
It should give this:
The text was updated successfully, but these errors were encountered: