From a0593e3aa9b19b9ca3c3881cbe0d9d207fe46d2c Mon Sep 17 00:00:00 2001 From: DanConwayDev Date: Tue, 26 Nov 2024 07:48:30 +0000 Subject: 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 --- tests/ngit_init.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests/ngit_init.rs') 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 { let cli_tester_handle = std::thread::spawn(move || -> Result<()> { let yaml_path = git_repo.dir.join("maintainers.yaml"); let mut file = std::fs::File::create(&yaml_path) - .expect("cannot create maintainers.yaml file"); + .expect("failed to create maintainers.yaml file"); write!( file, "\ -- cgit v1.2.3