Replies: 6 comments
-
Hmm, I get an error because we're passing |
Beta Was this translation helpful? Give feedback.
-
You can try [alias]
nitpick = """clippy --message-format=json-diagnostic-rendered-ansi --
-W clippy::pedantic
-A clippy::must_use_candidate
-W clippy::nursery
-A clippy::cognitive_complexity
-A clippy::missing_const_for_fn
-W clippy::decimal_literal_representation
-W clippy::deref_by_slicing
-W clippy::if_then_some_else_none
-W clippy::lossy_float_literal
-W clippy::missing_asserts_for_indexing
-W clippy::needless_raw_strings
-W clippy::precedence_bits
-W clippy::print_stderr
-W clippy::rest_pat_in_fully_bound_structs
-W clippy::same_name_method
-W clippy::semicolon_inside_block
-W clippy::unused_trait_names
""" with For a better solution, see https://doc.rust-lang.org/stable/cargo/reference/manifest.html#the-lints-section. |
Beta Was this translation helpful? Give feedback.
-
This worked, thank you, other than that I do want manually running |
Beta Was this translation helpful? Give feedback.
-
You can configure the lints in the manifest, then just run |
Beta Was this translation helpful? Give feedback.
-
Aren't manifests local to crates? The point of me defining nitpick was not wanting to have to do that |
Beta Was this translation helpful? Give feedback.
-
They are. But having to override the full command in r-a isn't ideal either. I'd write a script that calls |
Beta Was this translation helpful? Give feedback.
-
I have this alias in
~/.cargo/config.toml
:and these Helix settings:
Running
cargo nitpick
myself on a file likecorrectly outputs
But when Helix tries to run rust-analyzer's
check
, it says (followed by some other stuff that doesn't fit)Beta Was this translation helpful? Give feedback.
All reactions