CLI: Hide stack traces in errors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
When we throw an error in the CLI - an expected error anyway - we don't want to include a stack trace. It's unhelpful and a bit unprofessonal
I'd like a nice way to catch errors right at the top of the handler for all functions and work out if its an expected or unexpected error, and show the stack appropriately. A custom error class wold probably be enough, with a hideStackTrace flag.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CLI handler entry points and the existing error-catching behavior for its functions. Define how expected errors are identified and verify that they hide stack traces while unexpected errors still show them; the issue is done when this behavior applies consistently across the CLI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100