You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 57d9258
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(scan): name settings with tokens, not CLI flags, in engine messages
Engine messages said "Use -force" or "(-t)" whatever the front end. They
now use scan.Setting tokens ({force}, {max_queries}, ...) and each front
end renders them: the CLI via scan.FlagName (output unchanged), the TUI
via its form labels, pkg/subenum via Config field names, replacing the
regexp that guessed flags out of message text. report.Target takes the
renderer for verdict reasons. Tests check every Setting has a name in
each front end and that no engine string literal names a flag.
Fixes#100
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
8
8
## [Unreleased]
9
9
10
10
### Changed
11
+
- Engine messages no longer hard-code command-line flags. They name settings with neutral tokens (`scan.Setting`), and each front end renders them in its own terms: the CLI as flags (unchanged output), the TUI as its form labels ("Use Force to scan anyway", "invalid Exclude pattern"), and `pkg/subenum` as `Config` fields, replacing its regexp that guessed flags out of message text. A test fails if an engine message names a flag or uses an unknown token (#100).
11
12
- The scan engine always ends with exactly one done event, marked `Stopped` when the scan ended before testing any candidate (out of scope, recursion ceiling, failed preflight or wildcard check, a wildcard zone without `-force`, or Ctrl+C during those checks), so the CLI, the TUI and `pkg/subenum` handle one shape of ending instead of a channel that sometimes closes without one. `pkg/subenum`'s `Event` gains `Stopped`, and a stopped scan's `Stats` now include the queries its checks sent (#99).
0 commit comments