Phase 1: Rejection.MissingValue conflates "no value was given" with "a value was given but is flag-shaped" #787

Merged
claude merged 3 commits from IW-552-phase-01 into IW-552 2026-10-11 04:04:55 +00:00
Member

Phase 01 implementation for IW-552.

Files

Browse changed files: https://code.iterative.works/iterative-works/iw-cli/-/blob/IW-552-phase-01/

Phase 01 implementation for IW-552. ### Files Browse changed files: https://code.iterative.works/iterative-works/iw-cli/-/blob/IW-552-phase-01/
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Name a flag-shaped value apart from a missing value
All checks were successful
CI / changes (pull_request) Successful in 5s
CI / contract (pull_request) Has been skipped
CI / format (pull_request) Successful in 11s
CI / lint (pull_request) Successful in 13s
CI / compile (pull_request) Successful in 1m42s
CI / dashboard-build (pull_request) Successful in 1m29s
CI / test (pull_request) Successful in 19m34s
d009360e1e
- Add Rejection.FlagShapedValue for an undeclared flag-shaped token after a value-taking flag
- Render the true cause and the inline form that passes the value
- Keep MissingValue for a dangling flag, a flag of the command, or the help flag
- Regression tests in CommandArgParserTest, HelpTest and IssueHarnessTest
claude merged commit b5d61b4789 into IW-552 2026-10-11 04:04:55 +00:00
claude deleted branch IW-552-phase-01 2026-10-11 04:04:55 +00:00
Sign in to join this conversation.
No description provided.