chore: make it possible override clippy all (#1698)

* chore: make it possible override `clippy all`

* chore: fix clippy lints

* Update Cargo.toml

Cargo.toml

@@ -57,7 +57,8 @@ unused_extern_crates = "deny"
 
 [workspace.lints.clippy]
 type_complexity = "allow"
-all = "deny"
+# Priority -1 means that it can overwritten by other lints, https://rust-lang.github.io/rust-clippy/master/index.html#/lint_groups_priority
+all = { level = "deny", priority = -1 }
 # https://github.com/rust-lang/rust-clippy/issues/12643
 manual-unwrap-or-default = "allow"
 

metadata/src/lib.rs

@@ -441,7 +441,7 @@ impl StorageHasher {
     ///
     /// 1. A fixed size hash. (not present for [`StorageHasher::Identity`]).
     /// 2. The SCALE encoded key that was used as an input to the hasher (only present for
-    /// [`StorageHasher::Twox64Concat`], [`StorageHasher::Blake2_128Concat`] or [`StorageHasher::Identity`]).
+    ///    [`StorageHasher::Twox64Concat`], [`StorageHasher::Blake2_128Concat`] or [`StorageHasher::Identity`]).
     ///
     /// This function returns the number of bytes used to represent the first of these.
     pub fn len_excluding_key(&self) -> usize {

subxt/src/book/setup/codegen.rs

@@ -46,7 +46,7 @@
 //! Using the [`#[subxt]`](crate::subxt) macro carries some downsides:
 //!
 //! - Using it to generate an interface will have a small impact on compile times (though much less of
-//! one if you only need a few pallets).
+//!   one if you only need a few pallets).
 //! - IDE support for autocompletion and documentation when using the macro interface can be poor.
 //! - It's impossible to manually look at the generated code to understand and debug things.
 //!

subxt/src/tx/tx_client.rs

@@ -599,11 +599,10 @@ pub enum TransactionInvalid {
     ///
     /// # Possible causes
     ///
-    /// For `FRAME`-based runtimes this would be caused by `current block number
+    /// For `FRAME`-based runtimes this would be caused by `current block number`
     /// - Era::birth block number > BlockHashCount`. (e.g. in Polkadot `BlockHashCount` = 2400, so
-    ///   a
-    /// transaction with birth block number 1337 would be valid up until block number 1337 + 2400,
-    /// after which point the transaction would be considered to have an ancient birth block.)
+    ///   a transaction with birth block number 1337 would be valid up until block number 1337 + 2400,
+    ///   after which point the transaction would be considered to have an ancient birth block.)
     AncientBirthBlock,
     /// The transaction would exhaust the resources of current block.
     ///