NewChecker takes CheckerOptions instead of positional arguments (closes #78) #137

Merged
clawbot merged 1 commits from issue-78-checker-options into next 2026-10-04 12:19:32 +02:00
1 Commits
Author SHA1 Message Date
sneak 9158721425 NewChecker takes CheckerOptions instead of positional arguments (closes #78)
check / check (push) Waiting to run
NewChecker now takes *CheckerOptions (ManifestPath, BasePath, Fs), named
like ScannerOptions. A nil Fs still means the OS filesystem, as before and
as in ScannerOptions; nil options or an empty path return an error naming
the missing path.

Audit of the other exported constructors in mfer: NewManifestFromFile took
a filesystem and a path positionally; it now takes
*ManifestFromFileOptions (Path, Fs) with the same nil and empty rules.
NewBuilder and NewScanner take no arguments, NewScannerWithOptions already
takes options, and NewManifestFromReader takes one reader, which the style
guide exempts; these are unchanged.

Model: opus-5-5
2026-10-04 09:26:35 +00:00