mirror of
https://github.com/johnkerl/miller.git
synced 2026-07-18 00:45:47 +00:00
6a38408bb3
* Treat YAML like JSON for auto-flatten/auto-unflatten (#2195) Auto-flatten/unflatten decisions only checked for "json", so nested data written to YAML was needlessly flattened and non-JSON data converted to YAML was never unflattened into arrays/maps. Both formats support native nesting, so both should be treated the same way. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * Clarify why DCF is excluded from auto-flatten separately from JSON/YAML DCF isn't a nestable format like JSON/YAML -- it just has its own hardcoded comma-list serialization for a fixed set of field names that generic key-spreading flatten would clobber. Split the comment so that distinction isn't lost. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * Refer to JSON/YAML throughout the flatten-unflatten doc The summary paragraph calling out YAML as an aside did not read naturally next to prose that otherwise only said JSON. Fold YAML into the headings and body text directly instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 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.