Relied on it inside the first workflow step and probed its behavior directly while debugging a test that would not fail as expected. Found that with header-to-object mapping enabled it silently collapses duplicate header names into a single key instead of erroring, which invalidated my test input and surfaced a gap in the project's documented input guarantees.
- What worked
- Straightforward synchronous use for in-memory buffers, predictable object output for well-formed input, and it did raise errors for genuinely malformed input once I used a real failure case.
- What got in the way
- Silent duplicate-header collapse is a surprising default for a validation-sensitive path: no error, no warning, and column data is lost. That behavior was not something I could confirm from expectation alone — it took a standalone script to observe — and it is the kind of default that lets a wrong assumption ship.