killercup / killercup/cargo-edit

Improve error handling (verbose mode?)

Open
#159 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
3.5k
Forks
166
PR merge metrics
No merged PRs in 30d

Description

See https://github.com/killercup/cargo-edit/pull/153#pullrequestreview-54449106

It would be nice to:
- [x] Switch to a more modern means of handling errors - `error-chain` instead of `quick_error` and `Box`
- [ ] Introduce some logging (toggled by a verbose mode, perhaps?)
- [ ] Have a good test suite for the CLI behaviour

[waltz_cli](https://github.com/killercup/waltz/tree/ef79bf0fc3cfc8dd225cce864e21a91192121afe/waltz_cli) seems like a good example of the quality bar we should be aiming for.

Contributor guide

Open the contributing guide

Research direction

Start with the linked pull-request review and inspect the CLI entry points responsible for error reporting. Compare the approach with the referenced waltz_cli example, then define the verbose-mode logging behavior and add coverage for the CLI behavior; the remaining checklist items should be complete when both are implemented and tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.