coffee-tools / coffee-tools/coffee

fix the formatting error

Open
#260 0 comments 0 reactions 0 assignees View on GitHub
🐛 - bug P-medium
Dominant language
Rust
Stars
11
Forks
13
PR merge metrics
No merged PRs in 30d

Description

Having the following workflow

```
➜ ~ coffee nurse --verify
╭─────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ● Defects Affected repositories │
├─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ ● Global repository migration completed for the networks: testnet bitcoin _ │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────╯
! Warning: Coffee local directory is damaged, please run `coffee nurse` to try to fix it
➜ ~ coffee remote list
Error: CoffeeError { code: 1, msg: "Coffee found some defects in the configuration. Please run `coffee nurse` to fix them.\n If you are want to skip the verification, please add the `--skip-verify ` flag to the command." }
```

The error should be printed as the warning in the previous command.

Contributor guide

Open the contributing guide

Research direction

Reproduce the behavior with `coffee nurse --verify` followed by `coffee remote list`. Start at the CLI error-reporting path that formats the `CoffeeError`; done means the second command prints the configuration defect as a warning, matching the warning style from the previous command.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.