mirror of
https://github.com/nushell/nushell.git
synced 2024-11-25 09:53:43 +01:00
84e1ac27e5
# Description `cargo` somewhat recently gained the capability to store `lints` settings for the crate and workspace, that can override the defaults from `rustc` and `clippy` lints. This means we can enforce some lints without having to actively pass them to clippy via `cargo clippy -- -W ...`. So users just forking the repo have an easier time to follow similar requirements like our CI. ## Limitation An exception that remains is that those lints apply to both the primary code base and the tests. Thus we can't include e.g. `unwrap_used` without generating noise in the tests. Here the setup in the CI remains the most helpful. ## Included lints - Add `clippy::unchecked_duration_subtraction` (added by #12549) # User-Facing Changes Running `cargo clippy --workspace` should be closer to the CI. This has benefits for editor configured runs of clippy and saves you from having to use `toolkit` to be close to CI in more cases.
26 lines
688 B
TOML
26 lines
688 B
TOML
[package]
|
|
authors = ["The Nushell Project Developers"]
|
|
description = "Color configuration code used by Nushell"
|
|
repository = "https://github.com/nushell/nushell/tree/main/crates/nu-color-config"
|
|
edition = "2021"
|
|
license = "MIT"
|
|
name = "nu-color-config"
|
|
version = "0.97.2"
|
|
|
|
[lib]
|
|
bench = false
|
|
|
|
[lints]
|
|
workspace = true
|
|
|
|
[dependencies]
|
|
nu-protocol = { path = "../nu-protocol", version = "0.97.2" }
|
|
nu-engine = { path = "../nu-engine", version = "0.97.2" }
|
|
nu-json = { path = "../nu-json", version = "0.97.2" }
|
|
nu-ansi-term = { workspace = true }
|
|
|
|
serde = { workspace = true, features = ["derive"] }
|
|
|
|
[dev-dependencies]
|
|
nu-test-support = { path = "../nu-test-support", version = "0.97.2" }
|