diff options
| author | DanConwayDev <DanConwayDev@protonmail.com> | 2024-11-26 07:48:30 +0000 |
|---|---|---|
| committer | DanConwayDev <DanConwayDev@protonmail.com> | 2024-11-26 12:26:47 +0000 |
| commit | a0593e3aa9b19b9ca3c3881cbe0d9d207fe46d2c (patch) | |
| tree | 3482e7c558eff09cc91604ad6ddcd02cf2c94699 /tests/ngit_init.rs | |
| parent | 1332c625b75fce616e06b415c99a068bc45c8210 (diff) | |
refactor: err msgs 'cannot' > 'failed to'
in nearly all cases 'cannot' was used when an action was tried and
failed. 'failed to' is strictly better because:
* just because the action didn't work that time doesnt mean it
cannot work
* it is better at drawing the users attention to a problem
Diffstat (limited to 'tests/ngit_init.rs')
| -rw-r--r-- | tests/ngit_init.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/ngit_init.rs b/tests/ngit_init.rs index 1183b3c..4302524 100644 --- a/tests/ngit_init.rs +++ b/tests/ngit_init.rs | |||
| @@ -309,7 +309,7 @@ mod when_repo_not_previously_claimed { | |||
| 309 | let cli_tester_handle = std::thread::spawn(move || -> Result<()> { | 309 | let cli_tester_handle = std::thread::spawn(move || -> Result<()> { |
| 310 | let yaml_path = git_repo.dir.join("maintainers.yaml"); | 310 | let yaml_path = git_repo.dir.join("maintainers.yaml"); |
| 311 | let mut file = std::fs::File::create(&yaml_path) | 311 | let mut file = std::fs::File::create(&yaml_path) |
| 312 | .expect("cannot create maintainers.yaml file"); | 312 | .expect("failed to create maintainers.yaml file"); |
| 313 | write!( | 313 | write!( |
| 314 | file, | 314 | file, |
| 315 | "\ | 315 | "\ |