Input YAML File

2 VersionsInput

Parses YAML files from the bound directory and decodes each document into the typed t value the downstream port demands, streaming multi-document files one record at a time. For TOML use input_toml_file; for JSON Lines use input_jsonl_file.

How it fits

Typical backends

Decode each YAML document and forward the record as JSON.

Feed YAML-described prompts or settings into a local model.

Caveats

Hard constraintThe output carries the generic backend type, so every document across every file must conform to the single wired type; mixed-shape documents need a union, an optional wrapper, or a plain String output to defer parsing.
AccuracyScalar coercion is opinionated — recognised boolean and null spellings become typed values, and the rest fall through integer then float then string — so fields that look numeric coerce to numbers unless the source quotes them or the wired type forces String.
I/O contractA multi-document file streams each document as its own typed value in file order, and anchors, aliases, tags, and merge keys are resolved inline rather than preserved.
FallbackA file that fails to parse, or a document that does not match the resolved type, is logged and skipped rather than aborting the run; the bound slot is a directory that is not walked recursively.
State lifetimeThe bound slot, repeat, and fps are hot-swappable and a non-positive fps disables pacing; changing the slot restarts from the new directory.

Versions

f98f314cdefault
Perf: decode YAML node directly to typed Object (no JSON intermediate); drop nlohmann_json dep
5/10/2026