Closed Ryex closed 1 month ago
Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:
Proper conventional commit scoping:
If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin
If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error
[x] Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above
[x] README
is properly formatted and uses fenced in links with <url>
unless they are inside a [title](url)
[x] Proper usage of opts
table rather than setting things up with the config
function.
📑 Description
Prevent rustaceanvim from enabling clippy on it's own. This results in a bad config atm. and would clash with any user provided config / this packs config if it worked.
Add the
--no-deps
clippy arg to not lint dependencies by defaultℹ Additional Information
this would fix rustacenvim 's bad clippy config but we should still disable it because it on it's side because will overwrite ours when
load_rust_analyzer_settings
is called https://github.com/mrcjkb/rustaceanvim/pull/403