Subcommand dispatch: one parent-level handler for every command, and a check that the parent declares the dispatched subcommands #744
Labels
No labels
agent-ready
bug
contract
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs-human
needs-input
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/iw-cli#744
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found during IW-679 (shared subcommand runner). Follow-ups, verbatim:
Service,ServerandGateCommandrepeat the sameonParentbody (runParsed(declaration, rest, env)(_ => rejectMissing(declaration, env))); a namedSubcommandhelper would hold it once — review-phase-01-20261007-070528.md, composition warning.review-stateignores parent-level flags (iw review-state --bogusreportsMissing subcommand, but the other dispatchers reportUnknown flag).Subcommand.dispatch(parent, subcommands, …)does not enforceparent.subcommands == subcommands.map(_.declaration); Config, Gate and Issue have no exact unknown-subcommand test to catch a drift — review-phase-01-20261007-070528.md, architecture and testing warnings.core/test/ConfigHarnessTest.scala:1PURPOSE line says "now declared" (temporal wording) — review-phase-01-20261007-070528.md, style warning.Intake: needs-human
Workflow: waterfall
Reason: G8 waits for PR #746 (IW-679), which adds Subcommand.dispatch and runParsed and is not merged
Analysis: project-management/issues/IW-744/analysis.md on branch IW-744