Handle implementation defined behavior on input etc
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 95
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Currently, calling `get_command` without checking `has_command` invokes implementation defined behavior (i.e. in both currently present backends an exception).
- [ ] Find all cases in the code where such assumptions are made
- [ ] Check and handle such errors
- [ ] Come up with a uniform and clean way to handle such errors
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 searching for get_command and has_command usage across the codebase, then compare how the two current backends behave when a command is unavailable. Review every unchecked assumption, decide on a uniform error-handling approach, and verify that all identified input paths handle those errors consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100