wrangl

Overview ¶

Command wrangl is the data-layer-only entry point for tui-builder.

Usage:

wrangl <config.yaml> [pipeline-or-source-name] [flags]

pflag (via cobra) accepts flags in any position — `wrangl examples/foo.yaml --list` and `wrangl --list examples/foo.yaml` both work.

Examples:

wrangl --list examples/http_countries.yaml
wrangl examples/http_countries.yaml all_countries
wrangl --limit 5 examples/stream_l1.yaml l1
wrangl --pretty examples/http_countries.yaml all_countries

With a name, wrangl runs that pipeline (or source) and emits its result to stdout: JSON for a one-shot polled source, NDJSON (one JSON value per line) for a stream. Designed to pipe into jq, duckdb, miller, or any line-oriented downstream.

With no name, wrangl prints the same listing as --list: every defined source and pipeline, its kind, and its lifecycle. Useful when you've inherited a config and want to know what's available.

wrangl deliberately does NOT import internal/screen, internal/build, or any tuilib package. The data layer is architecturally independent of the TUI — running wrangl never compiles, links, or drags in any terminal-UI code. A CI check enforces this boundary.