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 --- src/lib/login/mod.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/lib/login/mod.rs') diff --git a/src/lib/login/mod.rs b/src/lib/login/mod.rs index d2725e7..00dbb17 100644 --- a/src/lib/login/mod.rs +++ b/src/lib/login/mod.rs @@ -61,12 +61,12 @@ fn print_logged_in_as( source: &SignerInfoSource, ) -> Result<()> { if !offline_mode && user_ref.metadata.created_at.eq(&Timestamp::from(0)) { - eprintln!("cannot find profile..."); + eprintln!("failed to find profile..."); } else if !offline_mode && user_ref.metadata.name.eq(&user_ref.public_key.to_bech32()?) { - eprintln!("cannot extract account name from account metadata..."); + eprintln!("failed to extract account name from account metadata..."); } else if !offline_mode && user_ref.relays.created_at.eq(&Timestamp::from(0)) { eprintln!( - "cannot find your relay list. consider using another nostr client to create one to enhance your nostr experience." + "failed to find your relay list. consider using another nostr client to create one to enhance your nostr experience." ); } eprintln!( -- cgit v1.2.3