Input TOML File

2 VersionsInput

Parses TOML files from the bound directory and decodes each document directly into the typed t value the downstream port demands, optionally looping. Use it to ingest TOML configuration into typed pipeline stages.

How it fits

Typical backends

Read a TOML document and forward the decoded record as JSON.

Feed TOML-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 type wired to the port; mixed-shape documents need that type to be a union or optional.
I/O contractTOML date, time, and datetime values are decoded as strings, so the wired type must declare those fields as String.
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.
LimitationThe 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

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