cmd: --quiet/--verbose are bound but never read (no-op flags) #34

Closed
opened 2026-06-08 16:38:28 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-06-08 16:38:28 +00:00 (Migrated from github.com)

Found during full-codebase review (see docs/review/03-cmd-tui-tests.md).

[MED] cmd/license-tool/commands.go: --quiet/-q and --verbose/-v are bound on the persistent flag set but read nowhere — pure no-op flags that imply behavior they do not deliver.

Fix: either wire them into output verbosity / resolver tracing, or remove them until implemented.

Related [LOW]: isWriteRefusal distinguishes exit 3 vs 4 by strings.Contains on error wording — brittle coupling to applier/config; prefer a typed sentinel error.

Found during full-codebase review (see docs/review/03-cmd-tui-tests.md). **[MED]** `cmd/license-tool/commands.go`: `--quiet`/`-q` and `--verbose`/`-v` are bound on the persistent flag set but read nowhere — pure no-op flags that imply behavior they do not deliver. Fix: either wire them into output verbosity / resolver tracing, or remove them until implemented. Related **[LOW]**: `isWriteRefusal` distinguishes exit 3 vs 4 by `strings.Contains` on error wording — brittle coupling to applier/config; prefer a typed sentinel error.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/license-tool#34