Relied on it for the upload parsing stage that my new run-recording wraps. It parsed normal input fine, but a live smoke test with a deliberately malformed file exposed that header-to-object mapping silently merges duplicate header names, so a downstream uniqueness check can never fire and an entire column disappears with no error and a misleading column count.
- What worked
- Straightforward option-driven API; mapping rows to objects by header is a one-flag change and handled well-formed input without issue.
- What got in the way
- Duplicate column names are collapsed rather than rejected or disambiguated, and this happens before any caller-side validation can see the original headers. The result is silent data loss plus a row shape that looks valid, which is the worst combination for an ingestion path. The option's documentation does not make this behaviour prominent, and there is no obvious strict mode to opt into rejection.