A dangling valued flag with no following value hard-rejects where it used to fall back to its default #550

New issue

Closed

opened 2026-09-13 09:07:08 +00:00 by mph · 2 comments

mph commented

2026-09-13 09:07:08 +00:00

Owner

iw kanon/feedback "Title" --type reports '--type requires a value.' and exits 1, where the previous hand-written helpers treated it as absent and --type fell back to Feature. consumeValue returns Rejection.MissingValue (core/model/CommandArgParser.scala:227). This is fail-safe, so it is reported rather than argued against, but it is a behaviour change worth confirming as intended.

Type: bug
Filed from: /home/mph/ops/kanon-DEVDOCS-246 on branch DEVDOCS-246

`iw kanon/feedback "Title" --type` reports '--type requires a value.' and exits 1, where the previous hand-written helpers treated it as absent and --type fell back to Feature. consumeValue returns Rejection.MissingValue (core/model/CommandArgParser.scala:227). This is fail-safe, so it is reported rather than argued against, but it is a behaviour change worth confirming as intended. --- **Type:** bug **Filed from:** `/home/mph/ops/kanon-DEVDOCS-246` on branch `DEVDOCS-246`

mph referenced this issue

2026-09-13 09:08:18 +00:00

A flag value beginning with a double dash cannot be passed, and the refusal reports it as missing #552

claude commented

2026-09-14 23:14:29 +00:00

Member

Intake: needs-human — not actionable as filed.

This issue asks only that the behaviour be confirmed as intended, and the repository already answers "intended", so there is no change left to build:

Two shipped tests pin a dangling optional valued flag as exit-1 MissingValue: core/test/OpenHarnessTest.scala:62-70 and core/test/StartHarnessTest.scala:72-80, both --prompt with no value — an optional flag that has a fallback, exactly the shape --type has.
The 2026-09-03 ruling recorded at project-management/issues/IW-463/implementation-log.md:1788,1829 holds one value-handling rule across all commands.

Left open for you rather than closed, because "confirm as intended" is your confirmation to give. If you agree, close it; if the old fallback should come back, that is a decision that reopens the IW-463 ruling and wants its own issue.

Not a duplicate of the siblings: #548 (last-wins on a repeated non-repeated flag), #549 (a multi-word value filling an operand) and #552 (a value beginning with --) are separate defects in the same function, and fixing none of them closes this one.

Intake: needs-human — not actionable as filed. This issue asks only that the behaviour be confirmed as intended, and the repository already answers "intended", so there is no change left to build: - Two shipped tests pin a dangling optional valued flag as exit-1 `MissingValue`: `core/test/OpenHarnessTest.scala:62-70` and `core/test/StartHarnessTest.scala:72-80`, both `--prompt` with no value — an optional flag that has a fallback, exactly the shape `--type` has. - The 2026-09-03 ruling recorded at `project-management/issues/IW-463/implementation-log.md:1788,1829` holds one value-handling rule across all commands. Left open for you rather than closed, because "confirm as intended" is your confirmation to give. If you agree, close it; if the old fallback should come back, that is a decision that reopens the IW-463 ruling and wants its own issue. Not a duplicate of the siblings: #548 (last-wins on a repeated non-repeated flag), #549 (a multi-word value filling an operand) and #552 (a value beginning with `--`) are separate defects in the same function, and fixing none of them closes this one.

claude added the

needs-human

label

2026-09-14 23:14:29 +00:00

claude referenced this issue

2026-09-15 00:16:39 +00:00

CommandArgParser: no test for a non-repeated flag given twice, and last-wins reverses the previous first-wins #548

claude commented

2026-10-15 12:55:51 +00:00

Member

Working as designed — closed by Michal in a human-review session.
A dangling optional valued flag is refused with MissingValue on purpose: OpenHarnessTest and StartHarnessTest pin it, and the IW-463 ruling records it. No change is wanted.

Working as designed — closed by Michal in a human-review session. A dangling optional valued flag is refused with MissingValue on purpose: OpenHarnessTest and StartHarnessTest pin it, and the IW-463 ruling records it. No change is wanted.

claude closed this issue

2026-10-15 12:55:51 +00:00