-
Notifications
You must be signed in to change notification settings - Fork 43
[Rust Analyzer] Assists (Code Actions) not showing up #170
Comments
Looks like code fixes fail to suggest, not sure if is the same problem as Assists not showing up |
atom-languageclient needs some work to support the latest LSP spec that rust-analyzer tends to use. I've added support for some of the more standard actions in #173. More work is needed to supporting the non-standard rust-analyzer actions but we're a step closer. |
After updating to the 1.0.0 release, code fixes fail to suggest for me. Just letting y'all know 😄 (Oh, and tooltips won't show up for standard library items) |
@slightknack Are you using atom-ide-base or atom-ide-ui?
I can't reproduce this. See the screenshot in the readme |
atom-ide-base. I have atom-ide-ui installed, but it's disabled. Let me know
if you need any other diagnostic/system info. Thanks!
I can't reproduce this.
It might go away with a system restart or something - if it doesn't, I'll try to track down the root of the issue.
…On Sat, Jun 19, 2021 at 9:17 AM Amin Yahyaabadi ***@***.***> wrote:
@slightknack <https://github.com/slightknack> Are you using atom-ide-base
or atom-ide-ui?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#170 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANCIUGSNX3XK4E3VOX77HSLTTRACJANCNFSM4M6PSRFQ>
.
|
Does it work if you temporarily enable atom-ide-ui? |
If I enable atom-ide-ui, nothing shows up, i.e. I get no lints at all. I'm
going to check my config / other packages, I'll get back to you on Monday
or Tuesday with what I find. Again, it could just be something gone askew
when installing the update, and I haven't had the time to seriously look
into it.
|
Rust analyzer have a bunch of Code Actions, before the 0.22.0-beta releases, when using the rust-analyzer the Code Actions suggestions showed up, but never worked and after 0.22.0-beta releases the suggestions never show up.
The not working part are probably a problem in
atom-languageclient
, but I'm not sure.The text was updated successfully, but these errors were encountered: