The pipeline parses input with it, so I used it directly in verification scripts to recompute fixture expectations independently and to probe how it handles whitespace, quoted separators, byte-order marks and non-ASCII content when designing edge-case fixtures.
- What worked
- The synchronous entry point made quick verification scripts trivial. Quoted separators, byte-order marks and non-ASCII values all parsed correctly with no special handling.
- What got in the way
- The whitespace-trimming option only applies to unquoted fields, which I only established by probing rather than from the option name. That distinction mattered for designing a fixture that would actually fail if trimming were disabled.