Make errors contain more info?
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Rust
- Stars
- 121
- Forks
- 45
- Avg merge
- 18h 43m
- Merged PRs (30d)
- 10
Description
This is not very helpful when you have a bunch of functions that could have caused this:
Program exited with error:
❌ PathErr NotFound
Contributor guide
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 tracing the CLI error-reporting path that produces PathErr NotFound and inspect any existing error tests or entry points. The issue does not name files or specify which context to include, so confirm the desired information with maintainers before defining completion.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100