diff options
| author | David Sherret <dsherret@users.noreply.github.com> | 2023-03-15 17:46:36 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-15 17:46:36 -0400 |
| commit | fb021d7ceff3f8b1d7cdb0c2bdd75ea07c0428d2 (patch) | |
| tree | 09cb2bf87bba760b1abf706e0b8faedc9c368bbc /cli/tools/coverage/mod.rs | |
| parent | ca51f4f6c058d16ac438ad75ac92e8954895f5aa (diff) | |
refactor: remove usages of `map_or` / `map_or_else` (#18212)
These methods are confusing because the arguments are backwards. I feel
like they should have never been added to `Option<T>` and that clippy
should suggest rewriting to
`map(...).unwrap_or(...)`/`map(...).unwrap_or_else(|| ...)`
https://github.com/rust-lang/rfcs/issues/1025
Diffstat (limited to 'cli/tools/coverage/mod.rs')
| -rw-r--r-- | cli/tools/coverage/mod.rs | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/cli/tools/coverage/mod.rs b/cli/tools/coverage/mod.rs index 05ad853f8..eaa087171 100644 --- a/cli/tools/coverage/mod.rs +++ b/cli/tools/coverage/mod.rs @@ -562,7 +562,10 @@ fn collect_coverages( ) -> Result<Vec<ScriptCoverage>, AnyError> { let mut coverages: Vec<ScriptCoverage> = Vec::new(); let file_paths = FileCollector::new(|file_path| { - file_path.extension().map_or(false, |ext| ext == "json") + file_path + .extension() + .map(|ext| ext == "json") + .unwrap_or(false) }) .ignore_git_folder() .ignore_node_modules() |