Commit 0ab34bd
committed
Run
In d257b8a we dropped our old
`rustfmt` per-file exclusion logic and replaced it with
`rustfmt_skip` tags in each previously-skipped files. This had the
unintended consequence of fully disabling `rustfmt` across the
`lightning` crate:
`rustfmt` operates recursively across files in any module it is
told to format. Previously, because we were running `rustfmt` on
each non-excluded file, this meant we wanted to exclude `mod.rs`
and `lib.rs` files - not doing so would result in the entire
module/crate being formatted. However, `cargo fmt --check` only
runs `rustfmt` once - on `lib.rs`. Because we added a top-level
`rustfmt_skip` in `lib.rs` this caused `rustfmt` to ignore it and
all modules.
Here we prepare to fix this by formatting
`lightning/src/routing/mod.rs`.rustfmt on routing/mod.rs/re-enable it on the routing mod1 parent 8a9419a commit 0ab34bd
1 file changed
+2
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | | - | |
2 | | - | |
3 | 1 | | |
4 | 2 | | |
5 | 3 | | |
| |||
11 | 9 | | |
12 | 10 | | |
13 | 11 | | |
14 | | - | |
15 | 12 | | |
| 13 | + | |
16 | 14 | | |
17 | 15 | | |
18 | | - | |
19 | 16 | | |
20 | 17 | | |
| 18 | + | |
0 commit comments