mirror of
https://github.com/johnkerl/miller.git
synced 2026-07-18 00:45:47 +00:00
a707a155f2
When the skip-trivial-records verb is in the then-chain, the CSV/TSV record-readers now silently skip trivial (all-fields-empty) input lines -- notably blank lines at the end of a CSV file -- instead of raising a fatal header/data length mismatch. The user has explicitly asked for trivial records to be skipped, so mlr now exits 0 in this case. The verb's CLI parser sets a new ReaderOptions.SkipTrivialRecords flag, which the CSV and TSV readers consult only on the would-be-fatal mismatch path, so: * Behavior without the verb is unchanged: blank lines still error. * Genuinely ragged non-trivial records still error even with the verb. * --allow-ragged-csv-input behavior is unchanged. Fixes #1535. Co-authored-by: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| doc.go | ||
| errors.go | ||
| flag_json.go | ||
| flag_types.go | ||
| flag_types_test.go | ||
| flatten_unflatten.go | ||
| mlrcli_util.go | ||
| option_parse.go | ||
| option_types.go | ||
| README.md | ||
| separators.go | ||
| verb_utils.go | ||
Datatypes for parsing the Miller command line, and the flags table.
pkg/climainis the flag-parsing logic for supporting Miller's command-line interface. When you type something likemlr --icsv --ojson put '$sum = $a + $b' then filter '$sum > 1000' myfile.csv, it's the CLI parser which makes it possible for Miller to construct a CSV record-reader, a transformer chain ofputthenfilter, and a JSON record-writer.pkg/clicontains datatypes and the flags table for the CLI-parser, which was split out to avoid a Go package-import cycle.