Brummel/Aura
1
0
Fork 0
Code Issues 31 Pull Requests Actions Packages Projects Releases Wiki Activity

Decide aura run arg-parse strictness: trailing args after 'run' are silently accepted #16

New Issue
Closed
opened 2026-06-04 20:55:42 +02:00 by Brummel · 0 comments
Brummel commented 2026-06-04 20:55:42 +02:00
Owner
Copy Link
Copy Source

Fieldtest 0010 (#8) found that 'aura run extra-garbage' prints the full JSON report and exits 0 — the arg parse keys only on the first token being 'run' and ignores the rest.

context: the 0010 cycle_scope said 'any other or missing subcommand -> usage + exit 2', which does not unambiguously cover 'run '. The binary chose the lenient reading; the strict reading (unexpected trailing token -> usage + exit 2) is equally plausible and is what a user who typos 'aura run --sweep' would expect (today they get a silent full run instead of a hint). Either ratify the lenient contract with a one-line rustdoc note on the aura crate, or tighten main to reject unexpected tokens.

depends on: nothing — a small CLI contract decision + doc/code one-liner.

Fieldtest 0010 (#8) found that 'aura run extra-garbage' prints the full JSON report and exits 0 — the arg parse keys only on the first token being 'run' and ignores the rest. context: the 0010 cycle_scope said 'any other or missing subcommand -> usage + exit 2', which does not unambiguously cover 'run <junk>'. The binary chose the lenient reading; the strict reading (unexpected trailing token -> usage + exit 2) is equally plausible and is what a user who typos 'aura run --sweep' would expect (today they get a silent full run instead of a hint). Either ratify the lenient contract with a one-line rustdoc note on the aura crate, or tighten main to reject unexpected tokens. depends on: nothing — a small CLI contract decision + doc/code one-liner.
Brummel added the idea label 2026-06-04 20:55:42 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BLOCKER
Core functionality blocked; preempts other selection
 bug
Observable misbehaviour
 feature
Substantial extension; no full spec required
 idea
Droppable; no commitment
No Label idea
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude (Claude) Brummel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#16
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?