Better warning on bad input
Open
Nobody has claimed this yet.
documentation
ux
- Dominant language
- Python
- Stars
- 141
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
If the path to a file is incorrect the response from the CLI prints out a long stack trace:
And ends with:
Could the CLI validate the input argument first and display a clearer message to the user
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 at the CLI argument handling and reproduce the behavior with an incorrect file path. Trace where the input is processed and where the stack trace is emitted. Done means invalid paths are rejected with a clear user-facing warning instead of the long stack trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100