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 eb0193f
Browse filesBrowse the repository at this point in the historyBrowse files
refactor: name each setting in one table across front ends (#160)
internal/scan/settings.go now holds one table giving every engine Setting
its CLI flag (also the config file key and SUBENUM_* suffix), its
pkg/subenum Config field and its TUI form label. FlagName, the new
FieldName and Label, and the Settings list are all derived from it, so
pkg/subenum's configFields map, the TUI's settingsWithoutField map and the
FlagName switch are gone.
TUI form fields with a setting take their label and flag from that table;
the others carry their own flag. Each field points at its savedConfig slot,
so initial values, and SUBENUM_*/config file seeding in withSettings, are
derived from formFields instead of a separate 17-case switch that silently
ignored unknown flags.
New tests fail when a setting, flag or form field is added in one place
but not the others: every setting has a unique flag, field and label; every
CLI flag is either wired into the TUI or listed as deliberately omitted;
every flag the TUI reads exists; and each flag seeds exactly its own field.
Flag names, config keys, messages and TUI labels are unchanged.
Not done here: collapsing the Options-to-Config copy and deriving
completion metadata from flags (issue steps 2 and 4).
Fixes#160
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LpkeXSPwrzd7ZCuX3no7gD
0 commit comments