Skip to content

Commit c22906b

Browse files
blyxyasflip1995
authored andcommitted
Fix CI formatting issues
1 parent 97d31c8 commit c22906b

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

book/src/development/defining_lints.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,17 +5,21 @@ and registration of the lint in Clippy's codebase.
55
We can use the Clippy dev tools to handle this step since setting up the
66
lint involves some boilerplate code.
77

8-
In our example, we're going to create a lint to detect functions named `foo` because it is a highly non-descriptive name for a function, so we want to trigger this and fix it early in the development process.
8+
In our example, we're going to create a lint to detect functions named `foo` because it is a highly non-descriptive
9+
name for a function, so we want to trigger this and fix it early in the development process.
910

1011
## Lint name
1112

12-
A good lint name is important, it is usually given by the issue you're fixing (in the **Lint name** field). If you're unsure if the name you chose fits the lint, you can check the [lint naming guidelines][lint_naming]. Don't worry, if the lint name doesn't fit, a Clippy team member will alert you in the PR process.
13+
A good lint name is important, it is usually given by the issue you're fixing (in the **Lint name** field). If you're
14+
unsure if the name you chose fits the lint, you can check the [lint naming guidelines][lint_naming]. Don't worry, if
15+
the lint name doesn't fit, a Clippy team member will alert you in the PR process.
1316

1417
If you're still unsure, you can ask on the [Zulip] or on the Github issue / PR.
1518

1619
---
1720

18-
We'll name our example lint that detects functions named "foo" `foo_functions`. Check the [lint naming guidelines][lint_naming] to see why this name makes sense.
21+
We'll name our example lint that detects functions named "foo" `foo_functions`. Check the
22+
[lint naming guidelines][lint_naming] to see why this name makes sense.
1923

2024
## Add and Register the Lint
2125

@@ -157,5 +161,4 @@ ask one of the maintainers.
157161

158162
[all_lints]: https://rust-lang.github.io/rust-clippy/master/
159163
[lint_naming]: https://rust-lang.github.io/rfcs/0344-conventions-galore.html#lints
160-
[clippy_team_members]: https://www.rust-lang.org/governance/teams/dev-tools#Clippy%20team
161-
[Zulip]: https://rust-lang.zulipchat.com/#narrow/stream/257328-clippy
164+
[Zulip]: https://rust-lang.zulipchat.com/#narrow/stream/257328-clippy

0 commit comments

Comments
 (0)