Bug
file still has a YAML delimiter field (default \\n in New()), but nothing in the read path uses it. A read always emits one record per file. Unknown-looking keys are not rejected, so delimiter: \"\\n\" in a pipeline is a silent no-op.
Where
internal/pkg/pipeline/task/file/file.go — Delimiter is on the struct and set in New(), with no other references.
Expected
Either split on delimiter when reading, or drop the field and reject it at load.
Found while auditing task READMEs in #96.
Bug
filestill has a YAMLdelimiterfield (default\\ninNew()), but nothing in the read path uses it. A read always emits one record per file. Unknown-looking keys are not rejected, sodelimiter: \"\\n\"in a pipeline is a silent no-op.Where
internal/pkg/pipeline/task/file/file.go—Delimiteris on the struct and set inNew(), with no other references.Expected
Either split on
delimiterwhen reading, or drop the field and reject it at load.Found while auditing task READMEs in #96.