about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-01-14 15:34:17 +0000
committerbors <bors@rust-lang.org>2023-01-14 15:34:17 +0000
commit91c8ecc5f9ac3b005a532e6d0809eb7682d05cf6 (patch)
treebb56b88cbcf33223d133d0baef5712cc5eb42517
parent97fb130fb253504615fec61d8b5cd510818da5e1 (diff)
parenta7db92574cf191444f5bbfdfcb89af5655e280c4 (diff)
downloadrust-91c8ecc5f9ac3b005a532e6d0809eb7682d05cf6.tar.gz
rust-91c8ecc5f9ac3b005a532e6d0809eb7682d05cf6.zip
Auto merge of #10201 - MariaSolOs:patch-1, r=dswij
Add missing arguments to `new_lint` example of `cargo` lints

changelog: Add missing arguments to `new_lint` code example.

From the surrounding text, it seems like this code example is missing the arguments to create a new `cargo` lint.
-rw-r--r--book/src/development/adding_lints.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/book/src/development/adding_lints.md b/book/src/development/adding_lints.md
index 8b4eee8c9d9..c6be394bd7d 100644
--- a/book/src/development/adding_lints.md
+++ b/book/src/development/adding_lints.md
@@ -146,7 +146,8 @@ For cargo lints, the process of testing differs in that we are interested in the
 manifest.
 
 If our new lint is named e.g. `foo_categories`, after running `cargo dev
-new_lint` we will find by default two new crates, each with its manifest file:
+new_lint --name=foo_categories --type=cargo --category=cargo` we will find by
+default two new crates, each with its manifest file:
 
 * `tests/ui-cargo/foo_categories/fail/Cargo.toml`: this file should cause the
   new lint to raise an error.