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 /src/bin/git_remote_nostr/list.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 'src/bin/git_remote_nostr/list.rs')
| -rw-r--r-- | src/bin/git_remote_nostr/list.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/bin/git_remote_nostr/list.rs b/src/bin/git_remote_nostr/list.rs index daff1b6..9171544 100644 --- a/src/bin/git_remote_nostr/list.rs +++ b/src/bin/git_remote_nostr/list.rs | |||
| @@ -163,7 +163,7 @@ async fn get_open_proposals_state( | |||
| 163 | } | 163 | } |
| 164 | Err(error) => { | 164 | Err(error) => { |
| 165 | let _ = term.write_line( | 165 | let _ = term.write_line( |
| 166 | format!("WARNING: cannot fetch branch {branch_name} error: {error}") | 166 | format!("WARNING: failed to fetch branch {branch_name} error: {error}") |
| 167 | .as_str(), | 167 | .as_str(), |
| 168 | ); | 168 | ); |
| 169 | } | 169 | } |