stop_on_unknown doesn't work
Open
bug
help wanted
- Dominant language
- Ruby
- Stars
- 259
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Explicit raises are now inside the block. The entire mechanism seems to have been neglected, as it's application is uneven.
Contributor guide
Research direction
Start by tracing the stop_on_unknown option-handling entry point and reproduce a case where explicit raises occur inside the block. Compare the behavior across the paths that handle unknown options, then verify that stop_on_unknown consistently produces the intended result without changing unrelated error handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100