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 8b908bb
Browse filesBrowse the repository at this point in the historyBrowse files
Check library ranges once and name TUI fields by label (#414)
Config.options re-checked Rate, MaxQueries and HitRate before calling
scan.Options.Validate, which checks the same ranges with different
wording. Drop the duplicates and keep only the negative checks that
must run before 0 is replaced by a default; a table test checks that
Validate's errors name the Config field. The resolver check stays in
the library, since its message names the Resolver field, which the
shared settings table has no entry for.
The TUI's num helper took a hard-coded label for most numeric fields;
it now takes the label from formFields, so parse errors always use the
on-screen name. A test covers every numeric field.
Fixes#414
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments