-
-
Notifications
You must be signed in to change notification settings - Fork 253
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
Remove opinionated rust-analyzer config from astrocommunity.pack.rust
#1109
Comments
Feel free to open a PR @boraarslan |
Most of what you point out makes sense. But I find myself disagreeing with the clippy bit. The pack is there to provide a default for new users of astronvim, who might not know how to configure an LSP. It should stay IMO |
@Uzaaft I'm not really opposed to defaulting to |
Let's document the |
Ahahahah, maybe you are right. I've updated the PR to include the documentation changes. |
Grazie Mille @boraarslan |
Is your feature related to a problem?
astrocommunity/lua/astrocommunity/pack/rust/init.lua
Lines 19 to 47 in b882cbb
There are multiple problems with this config.
astrocommunity/lua/astrocommunity/pack/rust/init.lua
Lines 29 to 32 in b882cbb
This is entirely wrong and useless. These options are not under "assist". The correct namespaces are
rust-analyzer.imports.granularity.enforce
andrust-analyzer.imports.granularity.group
astrocommunity/lua/astrocommunity/pack/rust/init.lua
Lines 38 to 43 in b882cbb
This just makes the inlay hints way too verbose. Most of the time, the lifetime elision hints are not helpful at all and just add noise.
astrocommunity/lua/astrocommunity/pack/rust/init.lua
Lines 33 to 37 in b882cbb
This is just a bad default. I'm not sure why this is disabled.
astrocommunity/lua/astrocommunity/pack/rust/init.lua
Lines 23 to 28 in b882cbb
This is controversial, to say the least. Using clippy as the check command causes very long feedback loops on larger projects as it's slower and heftier than
cargo check
.Describe the new feature
The default
rust-analyzer
configuration is adequate for most people. This opinionated configuration should be removed as it doesn't offer any benefits over the default one.Additional context
No response
The text was updated successfully, but these errors were encountered: